Windows support

Open
#316 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, git, powershell, python, vim
Domain
cli, operating-systems, tooling

Research direction

Start with the generated .vimrc and reproduce the reported behavior in gvim launched from PowerShell versus Git Bash on Windows Server 2019. Check the Vim Plug paths and the git-gutter and ultisnips failures; done means the configuration launches consistently and the affected plugins either work or are handled appropriately on Windows.

Written by the indexing model from the issue text.

Description

  • 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?

Dominant language
HTML
Stars
2.1k
Forks
208
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from editor-bootstrap/vim-bootstrap

All issues in editor-bootstrap/vim-bootstrap

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.