-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Reply Feature #83
Comments
In what kind of situation would this be better that using |
Currently we are 2 people active in the chat so referencing a person does not achieve anything. However, conversations tend to stray from one topics into multiple (at least for me) and sometimes responding to a specific comment makes it clear what you are talking about (it could also repeat what the other person said). We use that a lot in other group chats |
I use markdown quotes to do this. Adding a hash in front of a message could complicate the UI, right? I’ll try it out anyway: maybe make it an optional feature. |
I agree with @quackduck on that one, it would be ugly to have all the time a number in front of the message if it is only used in a very small fraction of all exchanges. |
Sadly I have to agree. From what I have seen so far I guess there is no way to have a personalized version of the chat, right? Everyone sees whatever is posted. Otherwise there could be settings to enable showing the has value and for example the time it was posted (and only people that enable it see this) |
No, that is possible! |
Another way to do this is to have some sort of trigger (tab-tab / left key / right key etc) that works on an empty prompt and display a markdown formatted reply directly on the prompt. Should be fairly easy with the term lib's autocomplete callback. |
While using devzat today we came up with the idea, that it would be nice to be able to reply to a comment of someone else!
It might be achievable through a small (like maybe 3 or 4 characters long) hash value shown in front of every message.
Typing
or something could work out nicely
The text was updated successfully, but these errors were encountered: