Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 27156:67194006cad8 v8.2.4107
patch 8.2.4107: script context not restored after using <ScriptCmd>
Commit: https://github.com/vim/vim/commit/a9725221ac4650b7e9219bf6e3682826fe2e0096
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jan 16 13:30:33 2022 +0000
patch 8.2.4107: script context not restored after using <ScriptCmd>
Problem: Script context not restored after using <ScriptCmd>.
Solution: Also restore context when not in a script. (closes https://github.com/vim/vim/issues/9536)
Add the 'c' flag to feedkeys() to be able to test this.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 16 Jan 2022 14:45:03 +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"