From: Kevin Rodgers <kevinr@ihs.com>
Subject: Re: C-x 4 b RET does not restores wrong other window
Date: 18 Apr 2002 15:18:52 -0600 [thread overview]
Message-ID: <wefads0d7sz.fsf@ihs.com> (raw)
In-Reply-To: 200204162016.g3GKGx524217@aztec.santafe.edu
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
rms@gnu.org (Richard Stallman) writes:
>ture@lysator.liu.se (Ture Pålsson) writes:
>> 1. Start emacs with emacs -q --no-site-file
>>
>> 2. Type C-x 2 C-x 2. This should give you three windows, all showing
>> the *scratch* buffer, with the cursor in the topmost one.
>>
>> 3. Type C-h f c o n s RET. This gives you the help text for 'cons' in
>> the middle window, and the text "Type C-x 4 b RET to restore other
>> window. C-M-v to scroll the help." in the echo area. The cursor is
>> still in the topmost window.
>>
>> 4. Type C-x 4 b RET. I expected this to switch the middle window from
>> the *Help* buffer back to *scratch*, but instead it switched the
>> bottom window from *scratch* to *Messages*.
>>
> When there are three windows, in general--there is no single command
> that will restore the proper window to its previous state. I am not
> sure what change to make to improve this situation. Do you want
> to work on it?
I thought that that winner-mode would handle this as requested, but
doing `M-x winner-mode' first and doing `C-x <left>' instead of `C-x 4
b' doesn't work either: it only changes the window-buffer
correspondence so that there are still 3 windows. Maybe winner-mode
should advise the describe-* functions, or with-output-to-temp-buffer,
to DTRT. (If so, print-help-return-message should have a clause to
detect winner-mode, and display the winner-undo key binding instead of
switch-to-buffer-other-window.)
--
Kevin Rodgers <kevinr@ihs.com>
prev parent reply other threads:[~2002-04-18 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 16:50 C-x 4 b RET does not restores wrong other window Ture Pålsson
2002-04-16 20:16 ` Richard Stallman
2002-04-18 21:18 ` Kevin Rodgers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wefads0d7sz.fsf@ihs.com \
--to=kevinr@ihs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).