From: martin rudalics <rudalics@gmx.at>
To: Geoff Gole <geoffgole@gmail.com>, 1322@emacsbugs.donarmstrong.com
Subject: bug#1322: dedicated *Help* and M-x help-for-help
Date: Mon, 10 Nov 2008 18:06:18 +0100 [thread overview]
Message-ID: <49186A0A.40601@gmx.at> (raw)
In-Reply-To: <f5bc73230811100233t52808d5ah6444f164e414195f@mail.gmail.com>
> Would it be ok to just work around this by giving the
> help-for-help buffer a title that is not "*Help*"? Most uses of
> special-display-buffer-names aren't going to cause this problem.
`help-for-help' pops up the *Help* buffer in a separate frame. Typing a
character now may cause its window display something else. Thereafter,
`help-for-help', recalling that it popped up a frame and wrongly
assuming that the user has finished viewing its buffer, decides to
iconify the frame.
So giving the `help-for-help' buffer another name ("title") should
indeed fix this and I initially thought to go that way. But, on the
other hand, we usually _want_ to reuse that frame for displaying other
help instead of having to deal with two separate help-related frames.
An easy solution is to use an extra variable, set by `help-for-help' and
reset by `with-help-window', to control iconification. But I never had
the time to check whether all functions run by `help-for-help' also run
`with-help-window'.
martin
next prev parent reply other threads:[~2008-11-10 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 10:33 bug#1322: dedicated *Help* and M-x help-for-help Geoff Gole
2008-11-10 14:57 ` Drew Adams
2008-11-10 17:06 ` martin rudalics [this message]
2008-11-11 2:28 ` Geoff Gole
2008-11-11 9:41 ` martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2008-11-10 4:47 David Reitter
2008-11-10 9:46 ` 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=49186A0A.40601@gmx.at \
--to=rudalics@gmx.at \
--cc=1322@emacsbugs.donarmstrong.com \
--cc=geoffgole@gmail.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).