You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm using cheatsheet.nvim and mostly use it to call/run my custom commands and functions.
The only annoying issue is that it always filled in the command line if the selection row is a command.
I think you designed it in this way to let users edit the commands before run it? But me personally (for 90% of time) don't need to edit commands and just need to run them immediately.
In my opinion, we can add another keybinding like <Ctrl-r> (or whatever you prefer) for filling the command line and keep the <ENTER> to execute commands directly.
The text was updated successfully, but these errors were encountered:
LinArcX
changed the title
It's better to execute commands directly.
Add another key-binding to execute commands directly.
Dec 16, 2021
Hi @LinArcX ! Thanks for the PR, but I added a more configurable way of changing the keybinds in 9716f9a which also adds Alt-Enter as a default keybind for directly executing commands. Rebinding is also possible, so if you want to use Enter to directly execute and Alt-Enter to fill the command line:
Hi. I'm using
cheatsheet.nvim
and mostly use it to call/run my custom commands and functions.The only annoying issue is that it always filled in the command line if the selection row is a command.
I think you designed it in this way to let users edit the commands before run it? But me personally (for 90% of time) don't need to edit commands and just need to run them immediately.
In my opinion, we can add another keybinding like
<Ctrl-r>
(or whatever you prefer) for filling the command line and keep the<ENTER>
to execute commands directly.The text was updated successfully, but these errors were encountered: