|
|
|
|
|
by eviks
1103 days ago
|
|
Return issue seems like VSCode specific? Does it manifest in Sublime? You also lose time on double checking typos in the term command (and it's harder to focus since unlike front¢er palette this command is tucked away at the bottom), except you have no additional validation from a preselected set, so you need to remember the full command invocation precisely And you can add special unique symbols to command names to make search unambiguous You also get a hint re keyboard shortcut, unlike with the term command, so if you execute it often enough, you might switch to a faster and more predictable method |
|
I have a fairly high typing accuracy on physical keyboards, in particular when I'm in a focused state, so I actually don't double-check editor commands most of the time -- I let them fail, which happens rarely, and only double-check them the second time.
And yes, in practice I use shortcuts mostly (although either vim extension shortcuts or custom ones, usually, because many shortcut don't work as is in the vim extension, so the command palette hint is useless to me as well - but I don't hold vscode responsible for that).