Re: Some annoying behaviours

[Thierry Volpiatto <thierry.volpiatto@gmail.com>]

Joe Fineman <joe_f@verizon.net> writes:

> Pete Axon <paxon@bigblue.net.au> writes:
>
>>> The first one is about the 'completion' window which doesn't close
>>> automatically once it's no more needed. I know I can switch to this
>>> window and close it but it would be really nice to make this auto.
>>
>> There is no need to switch to the other window, simply type `C-x 1'
>> and it maximizes the window you are in.
>
> That works if you had only one window on the screen to begin with.  If
> you had more than one (the usual case with me), the pop-up buffer
> commandeers an adjacent one.  I suppose C-x4 b would get the original
> buffer back, but then you would be in it instead of the one you were
> working in.  Fortunately, I usually have a brief command that sets up
> all the windows for the job I am doing.
>
> Also, I have a utility that saves the current window setup in case I
> expect to screw it up:
>
> (defun interruption ()
>   "Prepare to restore the existing state of the screen."
>   (interactive)
>   (if buffer-file-name
>       (save-buffer))
>   (save-window-excursion
>     (recursive-edit))
>   (if buffer-file-name
>       (save-buffer))
>   )
>
> It is bound to a function key.

Do you know winner-mode ?
When you have many windows open, do M-x winner-mode,
then come back to a single window (C-x 1) and then run 
M-x winner-undo ==> C-c left
come-back to the single window ==>C-c right (winner-redo)
-- 
A + Thierry
Pub key: http://pgp.mit.edu