You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my machine (Windows 8.1 x64) updating tags asynchronously launches a separate vim process every time, which loads one core entirely and never finishes. I just see a bunch of vim.exes in ProcessExplorer.
Notably, for some weird reason vim-shell launches Cygwin's vim, even though it is not the one that has precedence according to my PATH variable:
C:\Users\alepol> where vim
C:\Windows\vim.bat
C:\Program Files (x86)\Git\bin\vim
C:\cygwin64\bin\vim.exe
C:\vim74\vim.exe
Here the vim.bat script launches C:\vim74\vim.exe, as usual. I tried to search the sources as to where vim-easytags or vim-shell makes this decision, but quickly got lost in redirects...
The text was updated successfully, but these errors were encountered:
I updated vim-misc, vim-shell, and vim-easytags, and now the plugin calls the correct Vim executable. It is unable to find the DLL (which is a separate issue), but it is able to execute the client Vim with a correct command, which returns immediately. So, I'm closing this issue.
P.S. In order to make an async call without using the DLL, I had to make a fix to vim-misc: xolox/vim-misc#17
On my machine (Windows 8.1 x64) updating tags asynchronously launches a separate vim process every time, which loads one core entirely and never finishes. I just see a bunch of
vim.exe
s in ProcessExplorer.Here's the command for
vim.exe
:Notably, for some weird reason
vim-shell
launches Cygwin's vim, even though it is not the one that has precedence according to myPATH
variable:Here the
vim.bat
script launchesC:\vim74\vim.exe
, as usual. I tried to search the sources as to wherevim-easytags
orvim-shell
makes this decision, but quickly got lost in redirects...The text was updated successfully, but these errors were encountered: