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
I don't know if this is in-scope for your project, so here we go: Would you be open to adding further shortcuts?
I think the tool is great! Yet, more shortcuts, maybe with a nano-style explanation footer, would make it much more accessible. I just found the :O command in the tutorial which was exactly what I needed, however I do fear that when I use the tool in the future, I'll simply have forgotten on how to do that.
This is coming from someone who's never really used vim and is accustomed to being able to hit Ctrl+S to save (Which works even in nano nowadays).
Cheers!
The text was updated successfully, but these errors were encountered:
I understand your concern. The reason I chose the VIM style is that the majority of terminal guys that I knew were VIM users. Adding too many shortcuts, in my experience, makes the app convoluted and results in unwanted actions.
However, I have two future plans that may resolve your problem:
make the app customizable via a configuration file
In normal state (not registering command), pressing the space key enlists the possible key bindings.
Having a window pop up with a short help after pressing space would be great. As long it tells you that in the bottom row it's also easily discoverable :)
Hello!
I don't know if this is in-scope for your project, so here we go: Would you be open to adding further shortcuts?
I think the tool is great! Yet, more shortcuts, maybe with a nano-style explanation footer, would make it much more accessible. I just found the
:O
command in the tutorial which was exactly what I needed, however I do fear that when I use the tool in the future, I'll simply have forgotten on how to do that.This is coming from someone who's never really used vim and is accustomed to being able to hit
Ctrl+S
to save (Which works even in nano nowadays).Cheers!
The text was updated successfully, but these errors were encountered: