Skip to content
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

switch-to-buffer should not start on the current buffer #3513

Open
3 tasks
brosasaki opened this issue Sep 19, 2024 · 0 comments
Open
3 tasks

switch-to-buffer should not start on the current buffer #3513

brosasaki opened this issue Sep 19, 2024 · 0 comments
Labels
ui/ux Nyxt User Interface: themes, appearance and usability.

Comments

@brosasaki
Copy link

Purpose of request:
To improve the user experience when switching buffers.

Describe your proposed change:
When using switch-to-buffer, the current buffer should not be the initial focus of the highlight/pointer; either move it to the bottom of the list, or move the pointer by one increment.

Why do you believe this to be an improvement?
It would require one less button press to perform an action that is far more common (switching to the next buffer). There is little use case for switching to the currently-visited buffer.

Additional context/User story:
In Emacs, the switch-to-buffer command does not include the current buffer in the completion list (though it may be entered). Moreover, when using vertico-mode (which appears to have inspired Nyxt's interface), the current buffer is placed at the opposite end of the list from the initial pointer position.

Screenshots/Mock ups:
N/A


Pre-Build Checklist:

  • Discussion has occurred.
  • One or more developers have signed off on this change.
  • One or more user researchers have signed off on this change.
@brosasaki brosasaki added the ui/ux Nyxt User Interface: themes, appearance and usability. label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ui/ux Nyxt User Interface: themes, appearance and usability.
Development

No branches or pull requests

1 participant