"Project" is calling an autocommand for every BufEnter that resets
it's window size and position ( and so generally messes with all the
other windows in the process).

So far, I'm having good luck getting different app.s running in
various window layouts with WinWalker (the hard part being, getting
them to act right during subsequent manipulation).  I just tweaked it
to handle Taglist (which was setting bufhidden=delete).  If you want
to split it manually, use  :set bufhidden=  after you've opened
Taglist, and moved into it.

As a bit of fun, here is a mapping which will set up a similar window layout:

map ,tt <C-W>N:Tlist<CR>hn:Explore<CR><CR>l:edit
somefile<CR><CR><SPACE>asome stuff<ESC>

and here's a not-exactly-golden-ratio test layout :-)

map ,t <c-w>Nnvnvnv






On 4/21/06, Yegappan Lakshmanan <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On 4/21/06, Silent1 <[EMAIL PROTECTED]> wrote:
> > +-------+------------------------------+
> >  |       |                                 |
> >  |       |                                 |
> >  |Project|                              |
> >  |       |                                 |
> >  |       |                                 |
> >  |       |       edited file            |
> >  +-------+                              |
> >  |       |                                 |
> >  |       |                                 |
> >  |Taglist|                              |
> >  |       |                                 |
> >  |       |                                 |
> >  |       |                                 |
> > +-------+------------------------------+
> >
> > I'm wondering if the two vim scripts project and taglist could share a
> > vertical split like above? Taglist has an option to work with
> > vtreeexplorer, but i could not see anything with the project script.
> > Thanks in advance.
> >
>
> To use multiple plugins at the same time, you need to use the
> plugins with the winmanager plugin.  The taglist plugin works with
> the winmanager plugin. But the project plugin doesn't work with
> the winmanager plugin. This is a problem with the project plugin.
>
> You can try using the workspace plugin (instead of the project plugin)
> which works with the winmanager plugin.
>
> - Yegappan
>

Reply via email to