Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 17555:c2eb5118ba89 v8.1.1775
patch 8.1.1775: error message may be empty in filetype test
commit https://github.com/vim/vim/commit/eee9f65b2a213e9031f172d9d3b22adad6cb985d
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Jul 29 21:14:42 2019 +0200
patch 8.1.1775: error message may be empty in filetype test
Problem: Error message may be empty in filetype test.
Solution: Use v:exception instead. (Daniel Hahler, closs https://github.com/vim/vim/issues/4744)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 29 Jul 2019 21:15:08 +0200 |
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"