3

It looks like selecting something from that window leads to Windows doing Ctrl+V in an attempt to paste. That, of course, doesn't mean the same thing in Vim. However, if you have things properly set up to catch clipboard text in register * (see :h 'clipboard') then all you'd need to do after clicking an item in the window is hit p in Vim. (If that doesn't ...


2

It looks like you had the 'shellpipe' option misconfigured to just a | instead of a | tee (which would work on Linux/Unix/WSL) or > (which would work on Windows.) You can find the value this option is set to and the origin of this setting with: :verbose set shellpipe? As discussed in the comments, resetting this option to the Windows default worked to ...


2

EDIT: user Christian Brabandt points out that v:progpath will still only contain /usr/bin/vim when invoked through git-for-windows, so this solution will not work. Maybe something along these lines? if v:progpath =~ "git" colorscheme default endif The variable v:progpath should contain a path to the running vim executable, and (assuming that ...


1

Operator =~ will either ignore case or not depending on whether the 'ignorecase' option is set. You're trying to match a lowercase pattern, but the text you're matching contains an uppercase instance of the pattern. The 'ignorecase' option defaults to off, but is commonly set in one's init.vim, so I believe that's why you're getting different behavior during ...


1

The comments by B layer and Ben Knoble were both helpful in finding the answer. Vim correctly set the shell based on the $SHELL variable, but did not set shellcmdflag appropriately, and that was what the /s was, the default shellcmdflag for cmd.exe, as stated in the :help 'shell' file. Setting it to -c in my init.vim seems to have solved the problem, and a ...


1

So I found the issue and a workaround. The issue is on Windows the path separator is \ and not / as is written in the code. There is also a Windows in jasmine.vim when using the jasmine executable from within node_modules also related to path separators. I will raise a PR to the vim-test github repo to resolve this, but here is a workaround for windows: let ...


1

A new angle of attack: if has_key(environ(), "MINGW_PREFIX") && has_key(environ(), "GIT_INDEX_FILE") colorscheme default endif Poking around in help environ, it looks like has_key(environ(), <name>) is the recommended way of determining whether a system environment variable is defined. I'm not an expert on what ...


1

I believe it is simply the case that not all releases were/are signed. As such, if you are limited to only signed versions, you might not be getting the most recent build. Somewhat at odds with that is the fact that they list both signed and unsigned downloads under the same version number on github: https://github.com/vim/vim-win32-installer/releases From ...


1

Thanks to comment of muru. Solved the problem using https://vi.stackexchange.com/a/3729/33095 :nnoremap <Leader>w <C-w> Unless you've remapped , you can now use \w (after each other). I actually prefer this since I don't like CTRL+key combinations. and/or using https://vi.stackexchange.com/a/3737/33095. I actually use :wincmd more often than ...


1

My problem was I was trying to source my vimrc file within gvim/vim and my changes were not being applied in the session. I would have to reopen gvim/vim to see the changes. Adding the $HOME user environment variable: C:\Users\<username> resolved this. For my setup I am using Windows 10 and vim/gvim 8.2. Instead of using the user vimrc file: $HOME\...


1

filenameescape() is supposed to be the solution. And yet, I've cooked my own solution 2 decades ago and it's still working fine so far. function! lh#path#fix(pathname, ...) abort " Parameters {{{4 " Ignore the last slash or backslash character, if any let pathname = matchstr(a:pathname, '^.*[^/\\]') " Default value for the ...


1

Two solutions: On a current windows 10 machine that I have access to for work with a user account only, I was able to sucessfully install the standard vim version, named 'self-installing executeable' that is available here: https://ftp.nluug.nl/pub/vim/pc/gvim82.exe Administrator access was not required. This version comes with an autoload folder (unlike ...


Only top voted, non community-wiki answers of a minimum length are eligible