Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 29834:b772932fc721 v9.0.0256
patch 9.0.0256: compiler warning for uninitialized variables
Commit: https://github.com/vim/vim/commit/5214b294615718cc3f0d2248b76e9970b9fe9d45
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Aug 24 17:32:35 2022 +0100
patch 9.0.0256: compiler warning for uninitialized variables
Problem: Compiler warning for uninitialized variables.
Solution: Initilize the variables.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 24 Aug 2022 18:45:03 +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"