Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 11152:c780e3774dac v8.0.0463
patch 8.0.0463: side effects from resetting 'compatible' in defaults.vim
commit https://github.com/vim/vim/commit/0f39a82b07b285e0c54162e1038348b2988a715c
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Mar 16 14:19:36 2017 +0100
patch 8.0.0463: side effects from resetting 'compatible' in defaults.vim
Problem: Resetting 'compatible' in defaults.vim has unexpected side
effects. (David Fishburn)
Solution: Only reset 'compatible' if it was set.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 16 Mar 2017 14:30:04 +0100 |
parents | 584c835a2de1 |
children |
line wrap: on
line source
@rem @rem To use this with Visual Studio .Net @rem Tools->External Tools... @rem Add @rem Title - Vim @rem Command - d:\files\util\vim_vs_net.cmd @rem Arguments - +$(CurLine) $(ItemPath) @rem Init Dir - Empty @rem @rem Courtesy of Brian Sturk @rem @rem --remote-silent +%1 is a command +954, move ahead 954 lines @rem --remote-silent %2 full path to file @rem In Vim @rem :h --remote-silent for more details @rem @rem --servername VS_NET @rem This will create a new instance of vim called VS_NET. So if you open @rem multiple files from VS, they will use the same instance of Vim. @rem This allows you to have multiple copies of Vim running, but you can @rem control which one has VS files in it. @rem start /b gvim.exe --servername VS_NET --remote-silent "%1" "%2"