Windows – Starting vim from Windows PowerShell

powershellvimwindowswindows 7

This isn't necessarily a problem, I'm more curious why this behavior occurs.

When attempting to launch vim from powershell, I'm greeted with the Open with window:

PS C:\> vim

enter image description here

If I specify:

PS C:\> vim.exe

Vim launches as expected. gVim launches as expected no matter if I specify:

PS C:\> gvim.exe

PS C:\> gvim

Again, it's not really problem, I just want to know why it happens and what I should look into to get consistent behavior when launching both vim and gvim from powershell.

Best Answer

There's probably a file called vim. that appears in the Path before vim.exe (or it's in the local folder you're trying to launch vim from) so it's getting called first when you type vim.

Related Solutions

Linux – Preventing Windows version of Vim from destroying other file systems permissions

I'm pretty sure this is to do with differences in how permissions are handled on Windows and Unix/Linux. By default, files created on a Samba share from Windows always get created with 777 permissions. If backupcopy is set to no Vim saves files by creating a new file rather than writing to an existing one, so this would cause what you're seeing.

So, two possible fixes:

Set the backupcopy option in vim to yes
Set create mask = 0644 (or whatever) in the Samba configuration for the share in question

Info on file permissions in Samba

Fix YAML syntax highlighting in VIM

look at your vim7.3 installation directory under syntax/yaml.vim, roughly line 32:

syn region  yamlString      matchgroup=yamlStringDelimiter
                            \ start=+'+ skip=+''+ end=+'+
                            \ contains=yamlSingleEscape

if you throw that out, vim wont try to guess that ' is not the start of a string. the only other way imho would be to change the code so a ' only count as the start of a string, if the preceding character is a whitespace... but if you dont use ' as string-quote anyway, just throw out what i mentioned.

Best Answer

Related Solutions

Linux – Preventing Windows version of Vim from destroying other file systems permissions

Fix YAML syntax highlighting in VIM

Related Question