Mercurial > vim
view runtime/tools/vim_vs_net.cmd @ 12936:c53a80f39a52 v8.0.1344
patch 8.0.1344: using 'imactivatefunc' in the GUI does not work
commit https://github.com/vim/vim/commit/2877d334ad1321d1fcd5f903c0493bd0cdd787f8
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 26 14:56:16 2017 +0100
patch 8.0.1344: using 'imactivatefunc' in the GUI does not work
Problem: Using 'imactivatefunc' in the GUI does not work.
Solution: Do not use 'imactivatefunc' and 'imstatusfunc' in the GUI.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 26 Nov 2017 15:00:06 +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"