arkwright / vim-manhunt

Enhance vim-fugitive with easy diff browsing.
The Unlicense
10 stars 0 forks source link

E492 on fresh Windows install with Vim 7.4 #1

Closed Kazark closed 10 years ago

Kazark commented 10 years ago

I have Fugitive installed on Vim 7.4 on Windows 7 and I just used Pathogen to install Mahunt. When I do :Manhunt, I get:

e492-on-manhunt-first

and then the screen reloads and I see:

e492-on-manhunt

(BTW, I'm surprised this project didn't have any :star: until I starred it just now; it seems like a good idea!)

I do have lots of other plugins installed, but I am about to go home for the day so I won't post more details at this time. The plugin is at least partly operational still though after this. I am probably going to resume attempting to use this plugin after the holiday weekend and will try to post more details at that time.

arkwright commented 10 years ago

Thanks for the report, and your kind words!

I work exclusively on a Mac, so I'll have to procure a Windows 7 environment before I can reproduce this issue. It is very mysterious.

There is a decent chance of some kind of vimrc or plugin conflict. If you could disable everything else except for Pathogen and Manhunt, and give it another whirl, I would appreciate it very much.

Also, are there any other errors being output by :messages? If so, you can either send screenshots or use this one-liner to capture the output of :messages into register a:

:redir @a | silent! messages | redir END

arkwright commented 10 years ago

I discovered the source of the problem. :noswapfile does not work in gvim running Vim 7.4. It's also a new command added in Vim 7.4.something, so I'm going to look for a workaround because it would be nice to have 7.3 compatibility.

arkwright commented 10 years ago

I have fixed all of the Windows issues I could find, and published the fixes to the windows-fixes branch. I still have to update the documentation, but you can try our the changes if you like.

There is a swap file problem in gvim for Windows. The solution is to add :set dir=$TEMP to your _vimrc, as per these instructions:

http://choorucode.com/2010/01/14/vim-unable-to-open-swap-file/

There is also a diff problem with gvim 7.4 on Windows 7, which will produce E810 and E97 errors. Here is a fix that worked for me:

http://superuser.com/questions/697847/cant-run-vimdiff-7-4-on-windows-7

From now on I will try to test all of my plugins in Windows. Apparently there are lots of portability issues with Vim plugins. This has been a sobering experience!

Kazark commented 10 years ago

Much appreciated!! I will pull that branch as soon as I'm back in the office. Now I thought on Windows you could still do :set noswapfile... is that different?

arkwright commented 10 years ago

:set noswapfile is slightly different. The Vim help is confusing here, but it appears to be a setting that is toggled after creating a buffer. I was using :noswapfile to prevent a swap file from being created before the next buffer is created.

Anyways, I've switched to use :setlocal noswapfile in the windows-fixes branch. Thanks for the tip!

Kazark commented 10 years ago

Okay, I've got your windows-fixes branch and it seems to be working. So far I'm really digging this plugin!! I'm about to sit down and work with a coworker on digging through some changesets and I am eagerly anticipating impressing him once again with the kind of stuff you can do in Vim... ;)

Kazark commented 10 years ago

This plugin is great, and it's working fine for me on the Windows branch. From my perspective you can close this issue once you merge that branch. Thanks so much man! I always so much enjoy it when the author of something is so enthusiastic about it and fixes stuff so fast! Very impressed. Have been promoting this plugin to my buddy @mjgpy3.

arkwright commented 10 years ago

You're quite welcome, and thanks for the words of encouragement!

windows-fixes is merged into master now.

If you have any ideas for improvement, please don't hesitate to open an issue, because I'm intending to put much more work into this plugin.

Also, please let me know if I can leave you a bug finding credit in the help doc.

Kazark commented 10 years ago

Yeah, sure you can. I will definitely submit further issues as I come across or think of things!