What is the keyboard shortcut navigate back to the last cursor position in Visual Studio?
0
Add a comment
|
8 Answers
Ctrl+-
It will not work for the red color - key. For me it only works for the blue color combination.
5 Comments
Moesio
It in fact doesn't work with numpad 'minus' because it's another key indeed, although the characters be the same
Elshan
In visual studio 6 ( Visual C++ ) Shortcut key is
F2
Tobia Zambon
image is broken
Jim Aho
And
ctrl + shift + - for forward
Gulzar
@JimAho Only in VS the opposite of "-" is "shift+-"
According to Visual C# 2008 Keybinding Reference Poster it is Ctrl + -. The name of the specific keybinding is View.NavigateBackward.
PS: While researching I also found that Ctrl + . is the same as Shift + Alt + F10. Nice!
7 Comments
Ozkan
Whats the binding for 'next cursor position' then?
Protector one
@Ozkan:
Ctrl + Shift + -
LosManos
@Ozkan I believe means Ctrl-Shift-+
Dennis T --Reinstate Monica--
@LosManos, no it’s
Ctrl + Shift + - aka Ctrl, Shift and - pressed at the same time.LosManos
@Ozkan The binding for 'next cursor position' is ctrl-+ or (as I just learned after a typo) ctrl-shift--
|
ctrl + - (dash) navigates backward.
ctrl + shift + - (dash) navigates forward.
These settings can be found under Environment -> Keyboard:
1 Comment
Johan Boulé
Note that the default keyboard settings for the multiple installations i've done overs various versions have always been
ctrl + . and ctrl + shift + .. The former (navigate backward) is unaccessible for many nonqwerty keyboards, since you need to press shift to make VS realise that the key you're trying to send is the one with the . symbol on it (it's on the 2nd level). So, my answer is that there's is no default shortcut and you need to define it yourself.For Changing the setting in Visual Studio 2019:
- Search for view.navigate
- CHOOSE "Text Editor" from the "Use new shortcut in:" drop down menu
- Select your shortcut
Global doesn't catch for this.
Comments
For new VS Code(1.28.2)
Back: Ctrl+Alt+- (dash)
Forward: Ctrl+Shift+- (dash)
1 Comment
ratijas
Note that VS != VS Code. former is the IDE, other is an open source editor with plugins.
The most generic answers is: there is no working default and you need to define your own keyboard shortcuts for View.NavigateBackward and View.NavigateForward.
Why? For most keyboards, the default shortcut is a broken, unusuable combination because VS badly handles the shift and altGr modifiers. MS did not pay attention to portability and internationalisation so much when they redeveloped VS after version 6, and this is still true today. This bug has been there for way more than a decade, nearly two decades. At this rate, it will never be fixed. And yes, I have filled a bug report, and I'm certainly not the only one.
However, their "VSCode" product line does have better keyboard handling as it doesn't depend on the shift or altGr modifiers to identify the key. For example, when you are in text writing mode and press the key that has the dash symbol, without using shift nor altGr, let's say it writes something else, like number 6. To VSCode when it comes to shortcut handling, that's still the dash key for its purpose. As long as a key has the symbol written on it, whether this is painted as the 1st, 2nd or 3rd level doesn't matter, it just that key.
Of course, it's never a good thing to make the default shortcuts use non-alphanumeric symbols, that's always confusing, whether it works or not. The good mature text editors have known that for a long time and should be taken as examples of things done right. In some ways, VS learned a few good things from emacs with shortcuts that are a sequence of two letters, but ultimately screwed up on other parts with the choice of non-alphanumeric bindings, combined with a broken low-level keyboard handling.
Comments
On the top menu bar, right click and it'll give you an option -> 'command center'. See the arrow after you select it.
