Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!floyd!harpo!seismo!hao!hplabs!sri-unix!cmuitca!jag@cmu-cs-h.arpa@cmu-cs-h.arpa
From: jag@cmu-cs-h.arpa@cmu-cs-h.arpa
Newsgroups: net.emacs
Subject: Re: save-window-excursion
Message-ID: <16026@sri-arpa.UUCP>
Date: Thu, 26-Jan-84 10:24:00 EST
Article-I.D.: sri-arpa.16026
Posted: Thu Jan 26 10:24:00 1984
Date-Received: Sun, 5-Feb-84 13:26:20 EST
Lines: 27

From:  James Gosling 

   Could someone please explain to me why the fact that save-window-excursion
    "...does @i(not) save and restore the exact layout of the windows..."
   is considered a feature, not a bug? I find it amazingly annoying.

Well....  The effect I was trying to achieve was to not disturb the
state of windows that weren't exposed within the save-window-excursion.
For example,  Suppose I have one window on buffer A, and then I execute
this mlisp function:

	(save-window-excursion
		(pop-to-buffer "B")
		(recursive-edit))

Buffer B will appear on the screen, along with buffer A.  I can now
(say) move the window on buffer A to some other part of the buffer.
What should happen to the positioning of buffer A when I type ^C and
exit the recursive-edit?  What I tried to do (I say tried, since there
are some real bugs) is to have A not get repositioned when the
save-excursion exits, and to just have B vanish.

Someday, I'd like to get around to doing the "right" thing, whatever
that is.

				James.
-------