3 ms·
Cool. I mostly wanted confirmation that it’s better and not just a good substitute for disabled folks, RSI, etc. I’ll check it out. Does it mesh well with othe
by comfypotato 4y ago
Cool. I mostly wanted confirmation that it’s better and not just a good substitute for disabled folks, RSI, etc.
I’ll check it out. Does it mesh well with other VSCode functionality? I’m just wondering if you can use it in tandem with a normal keyboard.
- bgoated01 4y agoNot being a VSCode user myself outside of this context I may not have the best experience to answer the first question, but I don't think it tends to conflict with much except perhaps vim keybindings. As far as using it in tandem with a keyboard, the main issues you might run into are timing. If you happen to be moving the cursor or typing while a voice command is running it could cause issues. You would probably end up having to take a second to pause and wait for the command to finish before starting to use your keyboard. Other than that, you should be able to use the VSCode instance like normal at any point.
- comfypotato 4y agoThis is great. Thanks. It looks like this really shines for moving the cursor around: every important location in the code has a unique name. I wonder if I could port that functionality to emacs. It would take the place of avy (ace jump).
- pokeyrule 4y agoCheck out the #cursorless-everywhere channel in the Talon voice slack workspace; people are already working on an emacs port I'll also add that the cursor movement functionality, while quite useful as you get started, becomes less and less relevant as you get comfortable with the more advanced Cursorless commands for syntax tree manipulation