Re: [vimplugin-devel] VimEditor and VimEditorNewWindow

[Nageshwar <nag...@st...>]

Hi Sebastian,

>
> Could't we embed the _same_ gvim using "--socketid" in the different
> eclipse-editor-tabs all the time?  Then when the eclipse tab is
> changed, or a new editor is opened, we only create a new buffer in
> vim, select that buffer and we are done. The user should not notice
> what is going on behind the scenes (unless he did :buffers or
> similar). When Embedding is unchecked, we could use tabs instead.
>
We followed the same idea for standalone vim instance. But I didn't
check whether that is working or not. I don't think that the
"embedding same window multiple times" will work. Each window contains
only a single parent. As far as I know, the vim instance will appear
in the latest eclipse editor. I searched the same on the net but
couldn't find any relevant results. Anyway once please check it. Just
enable the embed vim option and open files in standalone vim.

> That would give a cleaner design (one editor class instead of three,
> where two of them are two-liners), a cleaner userinterface (only one
> vim-editor in the menu) and at last give a better performance (only
> one gvim running) ..
>
If it doesn't work, we have to modify the protocol and add a new
command to dynamically embed the window. But we can't do that since we
are using netbeans protocol implementation on vim.

> Getting technical: Is there an obvious way to send "normal" vim
> commands to vim? e.g. ":buf <bufid>"
>
This command is there in the protocol. Command is "setDot". We used it
when we get the focus on the eclipse editor tab.


-- 
Best Regards,
Nageshwar M.