view runtime/tools/vim_vs_net.cmd @ 17590:8d20183f2a8c v8.1.1792

patch 8.1.1792: the vgetorpeek() function is too long commit https://github.com/vim/vim/commit/dd00035cb52aa295d3ed3a93338ac04f2c8b35d0 Author: Bram Moolenaar <Bram@vim.org> Date: Fri Aug 2 21:35:33 2019 +0200 patch 8.1.1792: the vgetorpeek() function is too long Problem: The vgetorpeek() function is too long. Solution: Split off the part that handles mappings.
author Bram Moolenaar <Bram@vim.org>
date Fri, 02 Aug 2019 21:45:04 +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"