From: martin rudalics <rudalics@gmx.at>
To: Geoff Gole <geoffgole@gmail.com>
Cc: 1322@emacsbugs.donarmstrong.com
Subject: bug#1322: dedicated *Help* and M-x help-for-help
Date: Tue, 11 Nov 2008 10:41:29 +0100 [thread overview]
Message-ID: <49195349.80004@gmx.at> (raw)
In-Reply-To: <f5bc73230811101828t24d0397uebf8b8984e4eb6b@mail.gmail.com>
> I'm not sure this will be sufficient. Remember that help-for-help
> has entries that bring up info, NEWS, etc. Now if *Help*
> is the only thing in special-display-buffer-names and
> help-for-help is in it's own frame, accessing these help
> functions through help-for-help is going to spawn another frame.
>
> To see this:
>
> emacs -Q
> M-: (setq special-display-buffer-names '("*Help*"))
> f1 f1 C-a
> Return to first frame
> f1 f1 C-n
>
> Now there's four frames open!
Yes.
> Surely this is not the intended
> behaviour of help-for-help, even after fixing the iconification
> issue.
It is. `special-display-popup-frame', for whatever reason, has
(set-window-dedicated-p (frame-selected-window frame) t)
so C-a and C-n are not allowed to use the help window because they do
not put their information into *Help*.
> One way to work around that is to restrict help-for-help to the
> original frame in some way. If that is not acceptable then
> shouldn't we at least make sure that the user's commands are
> taking effect in the correct frame? It doesn't seem right that a
> help command will display differently when you run it through
> help-for-help.
We'd have to write our own `special-display-function' for that.
martin
next prev parent reply other threads:[~2008-11-11 9:41 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
2008-11-11 2:28 ` Geoff Gole
2008-11-11 9:41 ` martin rudalics [this message]
-- 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=49195349.80004@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).