view runtime/tools/vim_vs_net.cmd @ 23211:96a72f1f6c0c v8.2.2151

patch 8.2.2151: $dir not expanded when configure checks for moonjit Commit: https://github.com/vim/vim/commit/a79a8944dade9115ccaa5a06a076dfb257e56c62 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Dec 17 20:50:25 2020 +0100 patch 8.2.2151: $dir not expanded when configure checks for moonjit Problem: $dir not expanded when configure checks for moonjit. Solution: Use double quotes instead of single quotes. (closes https://github.com/vim/vim/issues/7478)
author Bram Moolenaar <Bram@vim.org>
date Thu, 17 Dec 2020 21:00:05 +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"