-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
'All messages' are not consistently accessible compared to P/#/f #1505
Labels
Comments
neiljp
changed the title
Hotkeys for 'all messages' are not consistently accessible compared to P/#/f
'All messages' are not consistently accessible compared to P/#/f
May 29, 2024
Hello @zulip/server-hotkeys members, this issue was labeled with the "area: hotkeys" label, so you may want to check it out! |
18 tasks
Niloth-p
added a commit
to Niloth-p/zulip-terminal
that referenced
this issue
Jun 6, 2024
This command worked only when a message was selected, using it as an anchor to fetch messages. Now, it has been made consistent with the other menu button commands, to work from any panel. This could not be implemented in ui.py along with other menu buttons, because of the conflict caused by the Esc key also being assigned to reset search in the side panels (GO_BACK command). When both operations, 1. reset search in the current panel view 2. narrow to all messages are possible, pressing `Esc` is set to trigger only the reset search operation and not the ALL_MESSAGES command. The next keypress of `Esc` will go to the home view once the current panel view is restored to its default state. Fixes zulip#1505.
Niloth-p
added a commit
to Niloth-p/zulip-terminal
that referenced
this issue
Jun 26, 2024
This command worked only when a message was selected, using it as an anchor to fetch messages. Now, it has been made consistent with the other narrow commands, to work from any panel. This could not be implemented in ui.py along with other narrow commands, because of the conflict caused by the Esc key also being assigned to reset search in the side panels (GO_BACK command). When both operations, 1. reset search in the current panel view 2. narrow to all messages are possible, pressing `Esc` is set to trigger only the reset search operation and not the ALL_MESSAGES command. The next keypress of `Esc` will go to the home view once the current panel view is restored to its default state. Fixes zulip#1505.
Niloth-p
added a commit
to Niloth-p/zulip-terminal
that referenced
this issue
Jun 28, 2024
This command worked only when a message was selected, using it as an anchor to fetch messages. Now, it has been made consistent with the other narrow commands, to work from any panel. This could not be implemented in ui.py along with other narrow commands, because of the conflict caused by the Esc key also being assigned to reset search in the side panels (GO_BACK command). When both operations, 1. reset search in the current panel view 2. narrow to all messages are possible, pressing `Esc` is set to trigger only the reset search operation and not the ALL_MESSAGES command. The next keypress of `Esc` will go to the home view once the current panel view is restored to its default state. Fixes zulip#1505.
Niloth-p
added a commit
to Niloth-p/zulip-terminal
that referenced
this issue
Jun 28, 2024
This command worked only when a message was selected, using it as an anchor to fetch messages. Now, it has been made consistent with the other narrow commands, to work from any panel. This could not be implemented in ui.py along with other narrow commands, because of the conflict caused by the Esc key also being assigned to reset search in the side panels (GO_BACK command). When both operations, 1. reset search in the current panel view 2. narrow to all messages are possible, pressing `Esc` is set to trigger only the reset search operation and not the ALL_MESSAGES command. The next keypress of `Esc` will go to the home view once the current panel view is restored to its default state. Fixes zulip#1505.
Niloth-p
added a commit
to Niloth-p/zulip-terminal
that referenced
this issue
Jul 18, 2024
This command worked only when a message was selected, using it as an anchor to fetch messages. Now, it has been made consistent with the other narrow commands, to work from any panel. This could not be implemented in ui.py along with other narrow commands, because of the conflict caused by the Esc key also being assigned to reset search in the side panels (GO_BACK command). When both operations, 1. reset search in the current panel view 2. narrow to all messages are possible, pressing `Esc` is set to trigger only the reset search operation and not the ALL_MESSAGES command. The next keypress of `Esc` will go to the home view once the current panel view is restored to its default state. Fixes zulip#1505.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
As discussed in the past, and again in #1480, the key(s) for 'all messages' (a, Esc ) do not work reliably except when a message is selected.
This compares with P, #, f, which are also in the top left list of views (as the web app now names/groups them), which are accessible from:
Discussed at:
#zulip-terminal > Make the ALL_MESSAGES command work everywhere
How is the bug triggered?
How can you reproduce the bug?
What did you expect to happen?
For context, when a message is selected, narrowing keys like these are currently expected to keep message focus, but change the narrow to view around it - this is not the intent for this fix.
Instead, when selecting a view/narrow explicitly (stream/topic/DMs/etc), from a side panel or hotkey from these locations, this should enter the first unread message in that view. This is what should already occur with the existing P/#/f hotkeys.
One possible challenge here is that Esc is used for various other functions, so they should likely take precedence, for example:
Similarly, when a text box is open, such as during searches or when the compose box is open, regular keys such as a would not be expected to cause narrowing.
Related aspects
These were discussed in the topic linked above:
GO_BACK
command may make it clearer in the help, compared to 'Go back'; otherwise this is somewhat of a refactor in the context of this issueHow are you running the application?
Please include as many of the following as possible:
eg. a specific version (0.7.0), or if running from
main
also ideally the git refeg. Zulip Cloud, the version you are running self-hosted, or the Zulip Community server (chat.zulip.org)
eg. Debian Linux, Ubuntu Linux, macOS, WSL in Windows, Docker
eg. 3.8, 3.9, 3.10, ... (implementation is likely to be eg. CPython, or PyPy)
If possible, please provide details from the
About
menu: (hotkey: Meta + ?)(this can provide some of the details above)
The text was updated successfully, but these errors were encountered: