I think I've got a clue now. Log on "wrong split behavior" https://gist.github.com/dezza/8f8a5d1932241c784f14
If I change the startdir to something else it seems to work (Not able to reproduce after several tries) .. Can anyone confirm this ? On 22 August 2013 21:25, Christoffer Aasted <[email protected]> wrote: > Hello Christian and thanks for answering. > > That's what I thought. I know you can test some auto-commands with > :debug wincmd p > and > :redir > :9verbose edit file.py > :redir END > > There is probably other ways to verify or debug this step-by-step. > > I made a verbose.log however: > https://gist.github.com/dezza/2808e71815b1a7072a76 > > If I remove all plugins except minibufexpl it works OK! > > If I re-add "mru.vim" I can go to one :MRU choose buffer (ENTER), then > type :e somefile.py and it does the same. > > If I re-add "mru.vim" and :e twice nothing happens. > > > > > > On 22 August 2013 20:49, Christian Brabandt <[email protected]> wrote: > >> On Mi, 21 Aug 2013, dza wrote: >> >> > hi guys, I've been using my vimrc for a few years and now suddenly >> > when I type ":e file" my minibufexpl splits up in three windows like; >> > http://i.imgur.com/ZTG5q17.png - it's quite random! Sometimes I can >> > reopen vim and do two ":e" and minibufexpl shows as normal, but >> > randomly it does this very annoying thing (usually when one file is >> > open and :e is issued). >> > >> > I've used minibufexpl for a few years and then I decided to install my >> > latest vimrc to my Windows and this startet happening. >> >> My bet is some autocommand. Does that happen with :noa :e? >> Do you have some suspicious Buf{Win}Leave or Buf{Win}Enter autocommands? >> >> regards, >> Christian >> -- >> Die Presse ist für mich Druckerschwärze auf Papier. >> -- Otto von Bismarck >> >> -- >> -- >> You received this message from the "vim_use" 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 >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "vim_use" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/vim_use/-epP4_mQWec/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > * > gplus.to/dza <http://gplus.to/dezzadk> // > ** > http://twitter.com/w0lfalot // > ** > http://facebook.com/psylifedk // http://w0lf.info // > http://quora.com/Christoffer-Aasted > > > * > -- * gplus.to/dza <http://gplus.to/dezzadk> // ** http://twitter.com/w0lfalot // ** http://facebook.com/psylifedk // http://w0lf.info // http://quora.com/Christoffer-Aasted // *folding@home<http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&teamnum=163&username=dezza> * * -- -- You received this message from the "vim_use" 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
