This post talks about how buffers takings over windows in Emacs is very horrible behavior. Based upon that feedback, it might be interesting to try out popwin.el.
You might also like some of these
4 thoughts on “Avoiding window takeover in Emacs”
As one of the comments in that thread mentions, winner-mode is a trivial answer to the general problem. A single keystroke will undo whatever it was that Emacs did to your window config.
It’s also incredibly useful for undoing *intentional* window configuration changes, of course — after all, you’ll have no hesitation in maximising a window for temporary readability when you know that a single keystroke restores the multi-split window config you started with.
…and it’s also worth pointing out that it’s not just the most recent change which is remembered — even after a whole series of window config changes, winner-mode enables you to step back through them all to get back to where you began. Just add (winner-mode 1) to your init file, and your life will be improved.
As one of the comments in that thread mentions, winner-mode is a trivial answer to the general problem. A single keystroke will undo whatever it was that Emacs did to your window config.
It’s also incredibly useful for undoing *intentional* window configuration changes, of course — after all, you’ll have no hesitation in maximising a window for temporary readability when you know that a single keystroke restores the multi-split window config you started with.
…and it’s also worth pointing out that it’s not just the most recent change which is remembered — even after a whole series of window config changes, winner-mode enables you to step back through them all to get back to where you began. Just add (winner-mode 1) to your init file, and your life will be improved.
PHIL:
Totally agreed. Thanks for sharing that.
Grant Rettke: Avoiding window takeover in Emacs: This post talks about how buffers takings over windows in Ema… http://t.co/0mMIMQaLlm