-
Notifications
You must be signed in to change notification settings - Fork 394
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
VsVim for Mac: Rename refactoring does not work #2763
Comments
I tried to reproduce this tons of times before and couldn't but I just tried and it reproduced the first time. I'll take a look at it as soon as I can. |
Were you able to figure this out? Enjoying the plugin but this one nit has me shifting between VsMac and vscode a lot. Can't wait to ditch electron! :) |
I've tried a bunch of different things to make it work, but have been unsuccessful so far as well. Definitely a large downside to what is an excellent plugin otherwise! |
Sorry about this. Haven't had time to look into it yet. |
|
Are any of you able to build the plugin from source code? I don't really understand how most of this code is intended to work yet... but it seems like switching the Switching the default setting from true to false seems to work. Not sure if there are any downsides. index ef236156..b96fb42d 100644
--- a/Src/VimMac/VimApplicationSettings.cs
+++ b/Src/VimMac/VimApplicationSettings.cs
@@ -124,7 +124,7 @@ namespace Vim.VisualStudio.Implementation.Settings
bool IVimApplicationSettings.EnableExternalEditMonitoring
{
- get { return GetBoolean(EnableExternalEditMonitoringName, defaultValue: true); }
+ get { return GetBoolean(EnableExternalEditMonitoringName, defaultValue: false); }
set { SetBoolean(EnableExternalEditMonitoringName, value); }
}
|
I don't fully understand why this works and didn't try to understand either. It seems like we should just not use this setting on MacOS (we don't have any 3rd party addins that can modify source code on Mac) Fixes VsVim#2763
I just built from source, happy to report that renaming succeeds. Just starting a coding session, will update if anything else breaks. |
I can also confirm that a build from source ( |
I don't fully understand why this works and didn't try to understand either. It seems like we should just not use this setting on MacOS (we don't have any 3rd party addins that can modify source code on Mac) Fixes VsVim#2763
I don't fully understand why this works and didn't try to understand either. It seems like we should just not use this setting on MacOS (we don't have any 3rd party addins that can modify source code on Mac) Fixes VsVim#2763
@kendallroth did you apply the diff above to master? Because master by itself doesn't contain the fix. Try and build from this PR if you can. Cheers. |
Ah, I did not. It works for a bit but eventually I am forced to close VS entirely and restart if I want to get it working. I've pulled from your repo now and will be checking again. |
Unfortunately I'm running into the same issue, where every now and again it "borks" itself and starts changing the variable name back when hitting |
Sadly, the fix doesn't work for me anymore either. After the first couple of successes reported above, the old behavior returned. |
I am too seeing this issue on my Mac that I'm not building from Source. |
I just happened to be debugging VSMac when I hit this error again. Making a note here for when I come to take another look
|
I think this PR is working now. Looks like I introduced an error in the last commit. |
Thanks! After encountering #2783 I built and installed from source, and a couple of test renames succeeded. |
Works for me as well. Got the latest via the update. Thanks for the fix! |
Migrated from #2733
Thanks for the plugin! I've run into the refactoring/renaming issue discussed above. On my mac, with VsVim enabled, doing a rename refactoring does not work. The text is highlighted, and I can enter the new name, but when I press enter, the highlight disappears and the old name returns. No changes occur.
I have to disable the VsVim plugin and restart VSMac for renaming to start working again. (The rename itself is sometimes buggy and garbles text, but that I assume is a separate VSMac bug.)
I am using the latest Preview build of VSMac 8.4 (build 2653) and a build from the current sources of VsVim following the instructions list in the above mentioned thread.
@nosami
The text was updated successfully, but these errors were encountered: