Description: Fix error message on double loading
If the file plugin/remoteOpen.vim is loaded twice by vim (e.g. at both local
and system-wide installation), errors about redefined commands are shown.
This patch should fix this.
Author: Johann Felix Soden <johfel@gmx.de>
Bug-Debian: http://bugs.debian.org/444426
commands to do the following:
1. change the EOL style of all vim files to be just LF.
2. changed the mime-type of all files to text/plain
3. removed the executable flag on all files.
This should hopefully make the repo look better on all platforms etc.
Why: The following vim command
:drop File Name with spaces
opens up multiple files.
Fix: escape() the file name before issuing the drop command.
NOTE: There is a vim bug where
exec "drop ".escape(filename, '\ ')
hangs GVIM.
Why: Vim eats up all but the last remote_send call when multiple
invokations to this function are made (Vim bug)
Fix: Collapse the entire set of keys into a single string and make a single
remote_send call.
would open it in a new session. But for projects with lots of
files, this can become painful. Therefore, instead of opening in
new sessions each time, open files in the same session we used the
first time we had to create a session.
from the command line as follows:
gvim -c ":RemoteOpen +<lnum> <filename>"
where <lnum> is the line-number you wish <filename> to open to. What will
happen is that a new gvim will start up and enquire from all previous
sessions if <filename> is already open in any of them. If it is, then it
will edit the file in that session and bring it to the foreground and itself
quit. Otherwise, it will not quit and instead open up the file for editing
at <lnum>.
This was mainly created to be used with Yap (the dvi previewer in miktex),
so you can specify the program for "inverse search" as specified above.
This ensures that the inverse search uses the correct gvim each time.
Gerd Wachsmuth
Till Maas
Johann Felix Soden
Srinath Avadhanula