view runtime/tools/vim_vs_net.cmd @ 32998:d55bf5bbcb6f v9.0.1791

patch 9.0.1791: No tests for the termdebug plugin Commit: https://github.com/vim/vim/commit/58f39d89a8adff51ab04893d1fd28e3767979f9f Author: Yegappan Lakshmanan <yegappan@yahoo.com> Date: Sun Aug 27 11:14:44 2023 +0200 patch 9.0.1791: No tests for the termdebug plugin Problem: No tests for the termdebug plugin Solution: Add some simple tests for the termdebug plugin closes: #12927 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
author Christian Brabandt <cb@256bit.org>
date Sun, 27 Aug 2023 11:30:06 +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"