cak@Purdue.ARPA (01/22/84)
From: Christopher A Kent <cak@Purdue.ARPA>
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.
Cheers,
chris
----------jag@cmu-cs-h.arpa@cmu-cs-h.arpa (01/26/84)
From: James Gosling <cmuitca!jag@cmu-cs-h.arpa@cmu-cs-h.arpa>
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.
-------