Re: [vimplugin-devel] VimEditor and VimEditorNewWindow

[Sebastian M. <seb...@un...>]

Am Sun, 14 Oct 2007 23:38:55 +1000
schrieb "Dave Terei" <dav...@gm...>:

> The two classes aren't about 'opening in an external window' or 'open
> embedded in vim'. That option is indeed as you suggested controlled
> by a setting in the preferences page.
> 
> The two classes are there for either:
> 
> 1) VimEditor class: This class will try to open the file using the
> default Vim instance. If this instance doesn't exist it will be
> created. Using this class multiple files can be opened in one vim
> instance.
> 
> 2) VimEditorNewWindow class: This class will always open a file in a
> new Vim instance which will only contain the one file.
> 

OK, I understand now. And it's explained well in the docs ... I got only
distracted by the name which suggests something else. How about
VimEditorNewInstance instead? 

> Using the second class we can easily embed vim into eclipse since
> each tab will contain its own vim instance. Using the first class
> gives better performance but doesn't embed into eclipse properly at
> the moment. If we use the first class we couldn't use Eclipses tabs,
> but we would be using Vim's tabs.

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.

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) ..

Getting technical: Is there an obvious way to send "normal" vim
commands to vim? e.g. ":buf <bufid>"

Seb.