-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Notify user if sent/edited message is outside current narrow #781
Comments
@kaustubh-nair Could you explain how I can resolve this?
|
@avats-dev You can use |
Thanks @kaustubh-nair for the help, I'll try and get back to you if I need some help. |
Hi @kaustubh-nair, I have a couple of questions:
|
1, That is correct. Though we want to give the user a pointer as to why the message disappeared from the screen. |
@zulipbot claim |
Welcome to Zulip, @zee-bit! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
This will set a footer text notifying the user everytime he sends or edits a message that is outside the current narrow. This will give the user a pointer as to why the message disappeared from the screen. Fixes zulip#781.
This will set a footer text notifying the user everytime he sends or edits a message that is outside the current narrow. This will give the user a pointer as to why the message disappeared from the screen. Fixes zulip#781.
This will set a footer text notifying the user everytime he sends or edits a message that is outside the current narrow. This will give the user a pointer as to why the message disappeared from the screen. Fixes zulip#781.
Hello @zee-bit, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days. If you've decided to work on something else, simply comment Thank you for your valuable contributions to Zulip! |
This will set a footer text notifying the user everytime he sends or edits a message that is outside the current narrow. This will give the user a pointer as to why the message disappeared from the screen. Fixes zulip#781.
This will set a footer text notifying the user everytime he sends or edits a message that is outside the current narrow. This will give the user a pointer as to why the message disappeared from the screen. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Tests amended. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Tests amended. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Fixes zulip#781.
This commit shows notifications in the footer if a message sent/edited by user is outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing check for user_id and message sender_id being the same. Fixes zulip#781.
This commit generalizes the code for footer notification when a message is sent/edited outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing the extra check for user_id being same as message_sender_id. Tests amended. Fixes zulip#781.
This commit generalizes the code for footer notification when a message is sent/edited outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing the extra check for user_id being same as message_sender_id. Tests amended. Fixes zulip#781.
This commit generalizes the code for footer notification when a message is sent/edited outside current narrow. This will give the user a pointer as to why the message disappeared from the screen. The code is hooked to the part where message request is sent to the server, hence preventing the extra check for user_id being same as message_sender_id. Tests amended. Fixes zulip#781.
For example, if a user is in topic narrow and edits a message's topic then it would be moved do a different narrow. We should probably display a message in the footer if this happens.
The text was updated successfully, but these errors were encountered: