On Wed, Nov 16, 2011 at 7:39 AM, Kerneels Roos wrote:
>
> Thanks for that info. OK, since 'putBufferNumber' is a Command-type message
> from IDE to editor (vim controller to vim editor) the format should be:
>
> {bufferNumber}:putBufferNumber!{seqno} {pattern}
>
> where all arguments in braces are mandatory Is this correct thinking? If so
> , then I tried this withoutt success:
>
> 0:putBufferNumber|123 "testBuffer"
The correct syntax is:
bufID:putBufferNumber!seqno "pathname"
Where bufID is the vim controller buffer number (so it should be '1'
in your example since it is the first buffer being registered to vim).
Note that the separator is '!' and not '|'
> Next step would be to unfortunately have to go look into the eclim code and
> try and gleen knowledge from thre since the documentation isn't providing
> enough examples. Would be nice to have a trace of a session including what
> vim received and sent in response. I suppose when vim is setup for debug
> mode with netbeans protocl some of that would be available?
Actually, when vim is setup for debugging netbeans, you get
information on what does the netbeans implementation. But it's easy to
infer from that information what is wrong with the message or what
message is being sent. You must be ready to read the code though :-(
Attached is the logfile of a simple pyclewn session
(http://pyclewn.sourceforge.net/) showing only the NBDEBUG level
entries. They are the netbeans messages exchanged on the socket.
On linux you can use this command to print the netbeans messages of a
running session (run as root):
tcpdump -i lo -s 2000 -A tcp port 3219
On linux and Windows you can also use wireshark to do this.
--
Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
logfile
Description: Binary data
