-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeat of :vsc commands not working #1314
Comments
You are correct that the edits perform by |
@cbilson I tried today something like yours |
Wow, I am really bad at replying to messages. Appologies. I just saw this. What I use is: map <Leader>rs :vsc ReSharper.ReSharper_SurroundWith<cr> I just tried it and it's not working for me either. I am pretty sure it did at some point, but maybe I am wrong. I have some other commands like this that definitely do work, for example: map <Leader>rf :vsc ReSharper.ReSharper_IntroduceField<cr> So, I am not sure what the issue with surround with is. |
Since |
I apologize in advance if this is not a bug or if it has already been addressed. I tried looking through the issues (open and closed) and didn't see anything like this.
I've created an alternate set of leader-prefix keyboard mappings and used those to drive resharper via the
:vsc
command. Here's a gist with an earlier version. I really love the:vsc
command, both because it lets me move the R# commands out of the way and still use them, and also because it makes several of them macbook keyboard friendly (and just wrist-friendly in general.)Before doing this, if I wanted to move a method up several slots in a class file, I might do
Alt+Shift+Up Arrow
several times until the method was in the right place. When I started using my new mapping, on instinct, I git dot (.
) after<Leader>mu
, expecting it to move the method up another slot.This didn't work.
I guess
:vsc
isn't technically a change (although the text in the buffer sure changed :-) ) so maybe this isn't supposed to work?Any ideas how I could get this to work?
The text was updated successfully, but these errors were encountered: