Skip to content
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

Windows support #316

Open
wasim42 opened this issue May 30, 2019 · 1 comment
Open

Windows support #316

wasim42 opened this issue May 30, 2019 · 1 comment

Comments

@wasim42
Copy link

wasim42 commented May 30, 2019

  • Vim bootstrap version(number in first line): Just got it from the website today
  • Operating system: Windows Server 2019
  • Vim/Nvim version: gvim 8.1.1
  • Languages: C, python, Go

I can get gvim to open with the vim-bootstrap configuration, but only if I edit the .vimrc file, replacing a couple of paths:

let vimplug_exists=expand('~/./autoload/plug.vim')

" ... skip a few lines

call plug#begin(expand('~/./plugged'))

to

let vimplug_exists=expand('~/vimfiles/autoload/plug.vim')

" ... skip a few lines

call plug#begin(expand('~/vimfiles/plugged'))

When I then call gvim from powershell, the plug-ins will install. However nothing works when I start the initial launch from git bash.

One thing I've noticed is that a number of the plug-ins don't work on Windows - such as git-gutter (messages about being unable to open temporary files in C:/Users/user/AppData/Local/Temp/5/RandChars.tmp while processing 143_git_supports_command_line_config_override) and ultisnips (constant reminders that it needs python installed).

Once they're out of the way I've found the system to be quite usable. Perhaps those plug-ins should be disabled if the user selects Windows for their OS?

@cassiobotaro
Copy link
Member

Can you point all plugins that don't work with windows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants