Vsvim: Ctrl + [ is not working in Visual Studio 2013

Created on 26 Oct 2013  Â·  25Comments  Â·  Source: VsVim/VsVim

I use Ctrl + [ instead of escape in Vim. I made sure I setup VsVim to handle Ctrl + [ instead of visual studio in the options and have restarted visual studio. It seems to me that Ctrl + [ is still being handled by visual studio since its asking for the second half of a chord instead of the expected Vim behavior. Any Ideas?

Most helpful comment

I have Japanese environment, and solved this issue.

  1. Download and Install ENU Language pack.
  2. Launch VS2013
  3. Change "tool >> options >> environment >> internationalization" to English mode.
  4. Restart VS2013
  5. Remove keyboard shortcut Ctrl+[ ("Solution Explorer" will appear with English mode)
  6. Restore internationalization.

All 25 comments

Unfortunately I don't have Visual Studio 2013 installed on the machine I'm currently on so I won't be able to look into this until tomorrow. As a quick check though you can go into the Visual Studio keyboard window and see if it has bound that command to something that VsVim missed.

  • Tools -> Options
  • Environment -> Keyboard
  • Navigate to the "Press Shortcut Key" box and type in the Ctrl+ sequence

If it is bound to a command it will show up in the drop down just below that dialog.

I experienced the same issue. It looks like Ctrl-[ is part of 3 or 4 commands (e.g. Image.PreviousColor) in that dropdown.

leemuro - if you remove the assigned commands listed in the dropdown (search for the names under "Show commands containing", then hit the "Remove" button for the selected command), then you'll get Ctrl+[ back in VsVim. (Of course you won't be able to use those Visual Studio commands unless you reassign them to another combination)

@tbombach it sounds like the key conflict resolution code just isn't picking up that combination. i will look into that and see why it's failing

Thanks guys, I'm not at my PC with 2013 on it right now but I will unmap those other Ctrl-[ shortcuts and see if that works.

For the record, unmapping the remaining Ctrl-[ shortcuts appears to work.

Thanks for verifying. I went to repro this bug yesterday and my 2013 RC
build had expired. Haven't had time to upgrade that machine yet to full
RTM. If manually removing the mapping works then I'm pretty sure I know
that the issue is.

On Thu, Oct 31, 2013 at 10:13 AM, barsae [email protected] wrote:

For the record, unmapping the remaining Ctrl-[ shortcuts appears to work.

—
Reply to this email directly or view it on GitHubhttps://github.com/jaredpar/VsVim/issues/1193#issuecomment-27505785
.

Jared Parsons
http://blogs.msdn.com/jaredpar
http://twitter.com/jaredpar

@jaredpar @tbombach
Hi
I met with the same issue.
I got the vsvim from MicroSoft official Visual Studio Extension gallary,and the version is 1.5.0.0.
I am sure the Ctrl +[ binding in vs is removed,but it seems this key combination can't be used by Vsvim.
Any help?

Created a Troubleshooting the Keyboard wiki page.

@ricksladkey

Thanks for the help.
It's weired that Ctrl+[ was removed,but it was still occupied by visual studio in 'background'
key
You see,there is nothing in the dropbox,but Ctrl+[ can not be used by vsvim.
Maybe it' s Visual studio 's issue

@lookforit when you removed that did it start working?

@jaredpar
Yes, I removed that keybinding, and it seems that 'Ctrl_[' is still taken by some function,but I cann't find it.
It's really strange in VS2013(I tried in VS2010,it works).

@lookforit that is strange. What locale are you running your OS / Visual Studio under?

@jaredpar
The OS is Windows 8.1 with Simplified Chinese language.
Also Visual Studio 2013 is under that language.

okay, I'll will try and investigate that this week and see if I can figure
out what is going on

On Tue, Jan 21, 2014 at 4:03 AM, Dennis Xiong [email protected]:

@jaredpar https://github.com/jaredpar
The OS is Windows 8.1 with Simplified Chinese language.
Also Visual Studio 2013 is under that language.

—
Reply to this email directly or view it on GitHubhttps://github.com/jaredpar/VsVim/issues/1193#issuecomment-32864618
.

Jared Parsons
http://blogs.msdn.com/jaredpar
http://twitter.com/jaredpar

@jaredpar Many thanks.
By the way ,the VS2013 is update to update 1 yesterday, but nothing changed for this issue.

@jaredpar
Hi, I found some keybindings begin with Ctrl+[ are used by VS Solution Explorer by defalt ,such as
Ctrl+[ Ctrl+p.
The most strange thing is I can not remove these keybindings,as which did not appear in the tools ->options->keyboard dialogue at all.
So I think the VS2013 is responsible for this problem,not Vsvim.

@jaredpar Hi,how is this issue going on?

I unfortunately haven't made any progress on this yet. I'm having trouble finding a non-english machine on which to reproduce this problem. It has to be a full OS with non-english in order to repro apparently.

Hi.
Just let you know that it reproduced in my Japanese environment.
As @lookforit said, Solution Explorer has some shortcuts beginning from <C-[> like a <C-[><C-o>.
It's listed on http://msdn.microsoft.com/en-us/library/da5kh0wa.aspx#bkmk_solutionexplorerGLOBAL.

Those shortcuts are not appear in the tools->options->environment->keyboard like he said.
It seems a bug of VS2013.

@supermomonga have you tried manually deleting / unbinding the key stroke from all of those Solution Explorer commands?

I have Japanese environment, and solved this issue.

  1. Download and Install ENU Language pack.
  2. Launch VS2013
  3. Change "tool >> options >> environment >> internationalization" to English mode.
  4. Restart VS2013
  5. Remove keyboard shortcut Ctrl+[ ("Solution Explorer" will appear with English mode)
  6. Restore internationalization.

@kuri65536 your solution also works in VS2015 with Simplified Chinese language
@lookforit you can try it.

@cosmoslx
yes,that's the point.
Actually,I posted the solution last year:
https://github.com/jaredpar/VsVim/issues/1309

@lookforit @kuri65536
aslo worked for VS 2019 community japanese .
Thanks

@lookforit @kuri65536
also worked for VS 2019 community traditional chinese
thanks

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DanielKeogh picture DanielKeogh  Â·  3Comments

iamkarlson picture iamkarlson  Â·  7Comments

deevus picture deevus  Â·  4Comments

MartinL0815 picture MartinL0815  Â·  6Comments

thelamb picture thelamb  Â·  5Comments