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

Missing shortcuts #2350

Open
mrx23dot opened this issue Feb 4, 2022 · 4 comments
Open

Missing shortcuts #2350

mrx23dot opened this issue Feb 4, 2022 · 4 comments

Comments

@mrx23dot
Copy link

mrx23dot commented Feb 4, 2022

Description of the problem or steps to reproduce

  • Please add F3 key to find next result, as it's very common
  • alt + mouse selection should do block (column) selection
  • ctrl+G should goto line (not bring up help menu)
  • ctrl+H could bring up help menu, or better replace menu
  • ctrl+End should jump to end of file, same for home, currently ignores ctrl

OS: deb10
Terminal: Version: 2.0.10
Commit hash: b976385

@gdevenyi
Copy link

gdevenyi commented Feb 4, 2022

I just came to ask something similar.

I would also accept repeated presses of Ctrl-F (or whatever is bound to find) to repeat the search to jump to the next result.

@mrx23dot
Copy link
Author

mrx23dot commented Feb 4, 2022

No default keybinding for replace command #2281

@nieware
Copy link

nieware commented Feb 23, 2022

I definitely agree with F3 for "find next" - all editors I know use it. Also Shift+F3 for "find previous".

@nieware
Copy link

nieware commented Feb 24, 2022

I checked it briefly now and adding F3 is easy, you just have to replace "F3": "Find" with "FindNext" in defaults_other.go. However "ShiftF3" or "Shift-F3" for "FindPrevious" doesn't work for some reason. When I press Shift+F3, "O2R" is inserted in the editor. Also "O2Q" for Shift+F2 and "O2S" for Shift+F4. No idea what's up with that...

Besides that, the UX for searching is a bit confusing. When you press Ctrl+F and enter a search term, the first found entry is already highlighted, but pressing Ctrl+N to find the next entry doesn't work. You have to press Enter to "confirm" the search text, then you can do "find next". Pressing Esc to close the Find (regex): prompt will cause Micro to "forget" what you entered and keep the previously entered search text (although it already "used" the new search text while you were typing it). This is all pretty confusing, so I would suggest the following:

  • no matter what key is used to close the search text box, the entered text should be remembered
  • The "find next"/"find prev" shortcuts should also work while entering the search text

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants