52

I am using Visual Studio 2015 and ReSharper 2016.2 and I have this strange behavior, that I probably activated (accidentally). When having the cursor in a line before the first word, hitting the Tab-key indents the line correctly:

enter image description here

When the cursor is inside of any word inside the line, hitting the Tab-key selects the word or block.

enter image description here

But the desired behavior would be to indent at the cursor (e.g. split a word into two words, if the cursor was inside of the word Stream after the letter r):

enter image description here

Does anyone know how this 'feature' is called? Does it come from ReSharper? Where can it be enabled or disabled?

Improve this question

3 Answers 3

Reset to default
73

Go to Resharper -> Options, in the left treeview select Editor Behavior and uncheck the last option Use Tab/Shift Tab keys for structural navigation.

enter image description here

Update for Resharper 2016.3.1.

Thanks to @Jordan for pointing this out!

Updated for Resharper 2016.3.1

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Still the correct answer for Resharper 2016.3.1 with the exception of an added option "The caret is in a comment or string literal."
Almost 7 years later and this answer is still relevant. Just saved me some headache when I couldn't figure out why hitting [Tab] in VS 2022 was not inserting space but instead selecting a block of code.
4

This is called Structural Navigation, and is really useful for tabbing between blocks of code, e.g. parameters in a method call/definition - makes it very easy to edit. The behaviour can be changed in the options, under Editor Behaviour. More details in the docs.

Improve this answer

Comments

0

Turn it off and use your pointer to "navigate" to the structure you want to edit. That way you can continue to add tabs to your comment blocks until they fix the otherwise useless feature. Somebody over there has too much time on their hands solving non-existent problems, and actually making things worse. They have the comment behavior of this "feature" listed as a bug. Should be fixed by 2018.

Improve this answer

1 Comment

Still not fixed in R# 2019

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.