Hey guys, I really love the product. The only issue I have is with using tab. My issue is that tab is pretty overloaded in my workflow already.
When I’m starting to do something new (write a new function, start a new “thought”) , I frequently want to insert a \t character. This is the point when cursor autocomplete is least useful because I haven’t given it enough information to be helpful yet. Yet, I hit tab and cursor will insert some something irrelevant.
Sometimes VS Code autocomplete is what I want, not cursor autocomplete. E.g., VS Code autocomplete is really good for completing long function or file names. It will pop up with a list of suggestions, I will hit Tab to accept, and the suggestion will be deleted and replaced with something irrelevant from cursor autocomplete.
Caps lock is a totally useless key. It should be the “AI button” on the keyboard.
Main thing I’m saying: cursor autocomplete is great, but there are edge cases where I don’t want it. These cases are situations where I am using the tab key disproportionately heavily (restructuring code, pulling in stuff from other modules).
I want to get a little sticker that says “cursor”, put it on the caps lock key, and never have this ambiguity.
Along these lines, I’ve been wanting to use a spacebar double-tap instead of tab. For those of us who use tabs over spaces, the behavior of cursor can be quite frustrating at times.
I agree that the caps-lock key is useless within the context of an IDE these days, however this could be confusing as it’s meant as a toggle switch.
Given the age old debate of spaces & tabs, allowing the user to choose between the tab-key or a spacebar double-tap for cursor autocomplete just feels correct.
Seconding this. I actually use the tab key to, you know, indent things. Indentation didn’t die with AI. I’m constantly accepting Cursor Tab suggestions by accident when trying to indent code. The Caps Lock key makes much more sense as the key for accepting suggestions. I know “Cursor Caps Lock” isn’t too catchy, so please just make it an option.
Making it so that Caps Lock doesn’t physically toggle the capitalization state (and caps lock light!) is something that has to be attacked at the OS level.
I solved this problem for myself (in a way that works across Windows, macOS, and Linux). It has worked out for me so well that I decided I should probably do the world a solid by writing it up, and then looking for other people who felt the same way, posting it on HackerNews, etc.
