Re: ibuffer kills split window

[Peter Lee]

>>>> John Paul Wallington writes:

    >> However if I'm working on 2 buffers (split), and I do C-x C-b,
    >> ibuffer takes over one of the buffers (whichever one did not
    >> have focus at time of call).  And when I press q, it buries the
    >> buffer and I lose the window... I have to resplit.

    John> I agree that's not good.  I'll try to solve the problem this
    John> week, but don't have the time now.  Patches welcome!
 
Great thanks!  I'll take a look at it as well, although my lisp isn't
very good.

    >> I much prefer the way bs-show did it by popping up a completely
    >> new buffer and when 'q' is pressed things are restored exactly
    >> as they were (even if I have 3 or 4 split windows).
    >> 
    >> I rely on ibuffer filtering though, so I'm hoping there's a way
    >> to get the old bs-show behavior.  If this is broken then is
    >> there a workaround?  If it's by design, then is it possible to
    >> get the old bs-show behavior through hooking and if so any
    >> ideas how I might do that?

    John> How about saying: (define-key ibuffer-mode-map "q"
    John> 'quit-window) ?

I initially did this only I used 'bury-buffer.  Each have there
problems.  quit-window will leave you with a split even if you didn't
have one previously.  Also there are cases where it doesn't remember
the last buffer and pressing 'q' takes me to *scratch*.

One other thing I noticed is if I have two split buffers say A on top
and B on bottom.  If im in A and do C-x C-b and choose a different
buffer say C, it puts C in the bottom window.  It's a bit
counter-intuitive.

I noticed these things a many months back when I first switched to
ibuffer (which is an awesome package btw) and just switched to using
the current window to display it.  But it would be awesome if it
could behave as bs-show did when in "use-own-window-mode".

Thanks John!