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
This is a suggestion that's not particularly needed but can be quite a boost in productivity if you are used to it. You can close this issue if you don't feel like ever implementing it for any reason, but I thought I'd at least share the idea.
The idea is that when this new command is executed, it assigns each open buffer with a key from the alphabet. Let's say I have three buffers open:
apple.md
orange.md
tomato.md
Now when this command is executed, it will assign each buffer with a key from a list of keys, like "qwerty", maybe. So, with that the buffers will look like this:
(q) apple.md
(w) orange.md
(e) tomato.md
If the user presses q after triggering the command, it will focus on the apple.md buffer, for example. Then after a successful operation it removes the key assignments.
It'd be cooler if the keys were persistent for each execution for buffers. I think a custom little hash function with some collision handling on the buffer names for indexing the key list can do the job, that'd make it reasonably smart. But my DSA isn't too strong so I wouldn't really know (maybe it makes no sense at all).
The text was updated successfully, but these errors were encountered:
This is a suggestion that's not particularly needed but can be quite a boost in productivity if you are used to it. You can close this issue if you don't feel like ever implementing it for any reason, but I thought I'd at least share the idea.
The idea is that when this new command is executed, it assigns each open buffer with a key from the alphabet. Let's say I have three buffers open:
apple.md
orange.md
tomato.md
Now when this command is executed, it will assign each buffer with a key from a list of keys, like "qwerty", maybe. So, with that the buffers will look like this:
(q) apple.md
(w) orange.md
(e) tomato.md
If the user presses
q
after triggering the command, it will focus on theapple.md
buffer, for example. Then after a successful operation it removes the key assignments.It'd be cooler if the keys were persistent for each execution for buffers. I think a custom little hash function with some collision handling on the buffer names for indexing the key list can do the job, that'd make it reasonably smart. But my DSA isn't too strong so I wouldn't really know (maybe it makes no sense at all).
The text was updated successfully, but these errors were encountered: