Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 29734:2d2f36e430f9 v9.0.0207
patch 9.0.0207: stacktrace not shown when debugging
Commit: https://github.com/vim/vim/commit/28c162f6f1f525882a9a60f10ab4836dee7eb59f
Author: zeertzjq <zeertzjq@outlook.com>
Date: Sun Aug 14 14:49:50 2022 +0100
patch 9.0.0207: stacktrace not shown when debugging
Problem: Stacktrace not shown when debugging.
Solution: Set msg_scroll in msg_source(). (closes https://github.com/vim/vim/issues/10917)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 14 Aug 2022 16:00: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"