Release for 2012

[jaredpar]

Change the manifest and build such that it can handle 2012 as well

[spacegaier]

I can now install it in VS2012, but the shortcut is not working. In your documentation it states that one should use "Ctrl+Shift+;". On my machine + locale&layout (system = German, VS IDE = English) that is the shortcut for zooming out (which is in fact "Ctrl+Shift+," [note: comma instead of semicolon] but on a German keyboard that results in the same combination).

The "Tools" menu states that "Ctrl+Shift+L" should be the correct shortcut instead:

However, that is the standard shortcut to delete the current line in VS, so that isn't working either. As a fix I can of course set a custom shortcut and then it works flawlessly. I am not sure if that is a VS2012 issue or just a general language/keyboard layout topic.

[jaredpar]

Unfortunately this is just a generic VS keyboard issue.

The original Easy Motion plugin that I was emulating uses the L version of the shortcut. Even though, as you noted, this is already mapped in most VS installations I kept it for familiarity of anyone that was used to the extension.

As for the German keyboard conflict that sound you heard is me swearing at my keyboard :(. There is unfortunately no giant master list of keyboard shortcuts. It varies from programming language, VS profile and actual UI language. It makes it nearly impossible to find a good truly unused shortcut to build upon when writing a new extension. Makes it tough on developers trying to keep it clean for everyone

Does it work if you remap it to a different key? That should work as Easy Motion uses standard command routing

[spacegaier]

Yes, as I wrote, using a custom shortcut set via the VS options works just fine. Just wanted to make you aware of the situation, although you probably cannot make anything about that.

[jaredpar]

Out of curiosity, what shortcut did u choose?

On Tuesday, October 14, 2014, spacegaier [email protected] wrote:

Yes, as I wrote, using a custom shortcut set via the VS options works just
fine. Just wanted to make you aware of the situation, although you probably
cannot make anything about that.

—
Reply to this email directly or view it on GitHub
#6 (comment).

Jared Parsons
http://blog.paranoidcoding.com/
http://twitter.com/jaredpar

[spacegaier]

"Ctrl+Shift+ö" which are the same keys on my German keyboard as the ones you use for "Ctrl+Shift+;" on your one.