Am I not supposed to use Tab when coding?

I really like Cursor, but at this point I’m actually considering changing to another solution simply because it’s insanely frustrating that Tab is default and can’t be rebound.

Am I missing something?
Am I not supposed to use tab when coding?

Right now I have it so that I’ve bound a key to enable and disable the copilot, but even then it’s still frustrating when I suddenly make a change rather than actually tab when it’s on.

Again, and I’m not being snarky - am I not supposed to use tab when programming? Because if so, how come Cursor decided that Tab is the accept key - and at the same time not include a way to modify it?

Finally, it feels kinda odd that I can’t change it in the first place - I’m running a whole ass different application instead of VSCode specifically for Cursor, am I to understand that even so it’s to hard to give the functionality of rebinding a key?

Again, not trying to be snarky - I’m genuinely not sure if missing something here, because I don’t get it.

9 Likes

I also find it a bit weird that I can’t tab in from the side of the editor, or to be more specific, I can if I wait for a certain amount of time (which I’m not sure yet exactly what it is) or alternatively do it very quickly! :sweat_smile:

2 Likes

I also find the inability to rebind the Tab key so frustrating it might be a deal breaker to not resubscribe to pro.

2 Likes

I’m curious on how to rebind tab key, although it doesn’t bother me in my actual execution it would be good to know how many settings are needed to change in order to actually rebind.

If you have a broken config that still results in “unable to rebind tab key” please post it. I can’t be arsed to update all my kebindings to be sure I’ve fully remapped tab (the 2nd to last one is funny to me)

1 Like

I did rebind all the bindings for “tab” to another key, and still pressing it triggers the cursor completions.

This is one such quality of life improvement that should take literally 1 minute to complete but saves users like me that 1 minute plus plenty of frustrations every single day.

2 Likes

I really hate that I can’t customize the key stroke to accept a copilot solution. As is currently, the action of tab key changes mid writing code. It makes me loose my train of thought. Net bad and will keep Cursors co-pilot off until they improve.

Came here after searching in vain for a way to remap Tab as the Cursor autocomplete key. Tab is such an incredibly overloaded key already, both for global system shortcuts like Alt-Tab, Cmd-Tab etc, and for the already existing VSCode Intellisense, as well as just inserting plain old tabs of course.

So a big +1 for being able to remap this.

1 Like

Yeah, I just realised I gave up using TAB to insert tab spaces, instead find myself waiting that quarter of a second longer until Cursor suggests I fix the indentation and tab then haha. Everything is taken care by “Format on save” anyway.

Where I really have difficulties is when autocomplete/intellisense pops up and fights with Cursor for control over my tab press. Terribly confusing.

Just created an account to say how frustrating this is… I cannot use intellisense now and have to rely only on Cursor to detect the correct change.

I cannot state how frustrating it is to try to use the VS Code autocomplete to write the correct stuff, but can have Cursor Tab overwriting everything with its suggestion. And the worst is the lack of key remapping!

Please, fix that, in the meantime I’m deactivating Cursor Tab and that’s definitly a deal breaker for me.