On 11 Okt., 13:54, "Wynand Marais" <[EMAIL PROTECTED]> wrote:
> Wow, Thanks for everyone's feedback :), there are some great ideas on how to
> get started. I particularly like the idea of running it as a server.
>
> > 2) You start the GUI version as Vim-Server. Used by gvimplugin [2].
communication using the --remote options:
----------------------------------------------------------------------------
--remote <Dateien> Editiere <Dateien> in einem Vim-Server falls
möglich
--remote-silent <Dateien> Dasselbe ohne Warnung, wenn kein Server
vorhanden ist
--remote-wait <Dateien> Wie --remote, aber warte, bis die
<Dateien> editiert wurden
--remote-wait-silent <files> Dasselbe ohne Warnung, wenn kein
Server vorhanden ist
--remote-tab <Dateien> Wie --remote, aber öffne ein Tab für jede
Datei
--remote-send <keys> Schicke <keys> zu einem Vim Server und beende
--remote-expr <Ausdruck> Führe <Ausdruck> in einem Vim-Server
aus und drucke das Ergebnis
--serverlist Drucke verfügbare Vim-Server-Namen und beende
--servername <Name> Benutze den Vim-Server <Name>
----------------------------------------------------------------------------
This is pretty simple but still, with --remote-send and --remote-expr
you can get some quite advanced "remote control" done.
The way it works is first start a server gvim with:
----------------------------------------------------------------------------
gvim --servername "Server Name" --remote-silent "File Name"
----------------------------------------------------------------------------
and then you send command to the server. Of example you can end the
server again with:
----------------------------------------------------------------------------
gvim --servername "Server Name" --remote-send ':xa<CR>'
----------------------------------------------------------------------------
or the following command will tell you if the file has been modified:
----------------------------------------------------------------------------
gvim --servername "Server Name" --remote-expr '&modified'
----------------------------------------------------------------------------
Since the gvim sending the command won't read any plugins performance
is quite ok.
> > 3) You start the GUI version as a Netbeans-Server. Used by eeedit [3].
Never used that but it seems quite powerful and with the (only one of
them)
----------------------------------------------------------------------------
--windowid <HWND> Open Vim inside another win32 widget
--socketid <HWND> Open Vim inside another win32 widget
----------------------------------------------------------------------------
you can even embed inside in you application.
Martin
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
