On 11/15/2011 1:51 PM, Xavier de Gaye wrote:
The current buffer, at the time the ':nbkey' command is issued, must
be a netbeans buffer (must have a 'bufID', registered with
'putBufferNumber').
Otherwise the buffer is unknown, and the keycommand is postponed
(queued) until the next 'putBufferNumber' command when the
'keyCommand' and 'keyAtPos' commands are sent for all postponed
keycommands. Note that there was a bug in the postponing
implementation that prevented it to work correctly, before vim 7.3.
Note that it makes sense that the buffer should be known, since the
cursor position is reported in 'keyAtPos'.
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"
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?
Any help or suggestions or more and better docs?
The best is setting up Vim so as to log netbeans protocol data
units (see ':help netbeans-debugging').
In the above test, you would have got the following message:
"got keycommand for non-NetBeans buffer, opening..."
OK, must do that then before looking at eclim source.
Thanks
--
Kerneels Roos
Cell: +27 (0)79 696 6038
Skype: cornelis.roos
--
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
