unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Kelly Dean <kellydeanch@yahoo.com>
Cc: 13146@debbugs.gnu.org
Subject: bug#13146: [PATCH] help-for-help interferes with buffer order, and displays help in too many windows
Date: Wed, 12 Dec 2012 10:42:21 +0100	[thread overview]
Message-ID: <50C8517D.6060905@gmx.at> (raw)
In-Reply-To: <1355252259.99571.YahooMailClassic@web141103.mail.bf1.yahoo.com>

 > M-x split-window RET C-x b foo RET C-x b bar RET C-h C-h C-g C-x b
 > It defaults to *Help*, but it should default to foo; transiently displaying help-for-help shouldn't modify the buffer order.

You're right.  It shouldn't.

 > Now do C-g C-h f mark RET C-x o C-h C-h
 > It shows the help-for-help page in both windows, but it should show it in only one.

This look quite silly, indeed.

-		     (switch-to-buffer-other-window "*Help*")
+		     (if (not (equal (buffer-name) "*Help*")) (switch-to-buffer-other-window "*Help*" t))

Using t as NORECORD argument is correct IMO.  Checking whether *Help* is
current is not quite correct (the current buffer is not necessarily
displayed in the selected window) but good enough for interactive use.
I think a simple `pop-to-buffer' would suffice here.

But I'm not sure whether `help-for-help' should use *Help* in the first
place.  A user might want to consult `help-for-help' and continue/resume
watching the current help information.  Does anyone see a downside to
renaming the buffer used by `help-for-help' to *help-for-help* (with a
leading space)?

martin





  reply	other threads:[~2012-12-12  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 18:57 bug#13146: [PATCH] help-for-help interferes with buffer order, and displays help in too many windows Kelly Dean
2012-12-12  9:42 ` martin rudalics [this message]
2012-12-13  8:12   ` Kelly Dean
2012-12-14 10:24     ` martin rudalics
2012-12-16 11:58 ` Kelly Dean
2012-12-17 13:38   ` martin rudalics

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=50C8517D.6060905@gmx.at \
    --to=rudalics@gmx.at \
    --cc=13146@debbugs.gnu.org \
    --cc=kellydeanch@yahoo.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).