From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, 19012@debbugs.gnu.org
Subject: bug#19012: 25.0.50; `help-window-select'
Date: Mon, 10 Nov 2014 10:23:13 -0800 (PST) [thread overview]
Message-ID: <8e78202d-5ac0-4df5-8195-9849dd7509b7@default> (raw)
In-Reply-To: <5460F5B3.6040402@gmx.at>
> > The description of `other' in the Customize buffer (and the doc
> > string) is incorrect. Or else the behavior is bugged.
> >
> > If *Help* is shown in its own frame (e.g. from *Help* being a
> > special-display buffer), and if the option value is `other' (the
> > default), then the *Help* window (and frame) are *not* selected,
> > in contradiction to what the doc says.
> >
> > On MS Windows, at least, if the *Help* frame in this context does
> > not yet exist then yes, that frame (and thus the *Help* window is
> > selected - the frame gets the input focus. But that is because
> > Windows always gives a newly created frame the focus. And if the
> > frame exists already then no, the *Help* window and its frame are
> > not selected. Focus stays with the frame where you invoked the
> > help command.
>
> It does get selected here on Windows XP. What happens when you set
> `help-window-select' to t?
The help window is still not selected.
> Did you create the *Help* window with `with-help-window'?
> If so, please tell me the value of the 'quit-restore window
> parameter of the *Help* window.
No, I guess not (see below), but I'm not sure.
And I did not read the note in the doc saying, "This option has
effect if and only if the help window was created by
`with-help-window'" (That sentence is missing a period, BTW.)
Mea culpa.
So I guess maybe what I said in the bug report about the behavior not
matching the doc is wrong (i.e., is irrelevant). The part about the
doc not being too clear might still help you, however. If not, I
guess you can close the bug.
I am on Windows 7 (but on XP the behavior was the same).
This is the relevant code:
(add-to-list
'special-display-buffer-names
(list "*Help*" '1on1-display-*Help*-frame
(list (cons 'background-color 1on1-help-frame-background)
(cons 'mouse-color 1on1-help-frame-mouse+cursor-color)
(cons 'cursor-color 1on1-help-frame-mouse+cursor-color)
'(height . 40))))
(defun 1on1-display-*Help*-frame (buf &optional args)
"Display *Help* buffer in its own frame.
`special-display-function' is used to do the actual displaying.
BUF and ARGS are the arguments to `special-display-function'."
(let ((old-ptr-shape (and (boundp 'x-pointer-shape) x-pointer-shape))
return-window)
(when (boundp 'x-pointer-xterm) (setq x-pointer-shape x-pointer-xterm))
(setq return-window
(select-window (funcall special-display-function buf args)))
(raise-frame)
(setq x-pointer-shape old-ptr-shape)
return-window))
Does that mean that `with-help-window' is not involved? Maybe so,
but it's not obvious to me. How is a user supposed to know whether
this option applies, i.e., whether "the help window was created by
`with-help-window'?
And why shouldn't such an option apply in general for the help window?
Why must it depend on how the window is created?
> > Note too that the description is anyway inadequate, because it
> > seems to make the assumption that there *is* another window on
> > the help window's frame: "unless the selected window is the only
> > other window on the help window's frame" is not clear for the
> > case where there is no such other window.
>
> When there is "no such other window" the selected window "is not the
> only other window on the help window's frame". What am I missing?
Maybe so, but it's not very clear, IMO. The vacuous case should be
mentioned explicitly, I think, and not depend for its understanding on
finessing the logic. Just say, for value `other', that "if the help
window is alone in its frame then it is selected".
With the scenario I described (*Help* is alone in its frame, in a
dedicated window, and the *Help* frame exists prior to calling the
help command) and with a value of `other' or `t', the *Help* window
is *not* selected.
With your interpretation, the "unless" condition is false, so the
*Help* window should be selected (except that perhaps
`with-help-window' is not involved - dunno about that).
next prev parent reply other threads:[~2014-11-10 18:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:42 bug#19012: 25.0.50; `help-window-select' Drew Adams
2014-11-10 17:28 ` martin rudalics
2014-11-10 18:23 ` Drew Adams [this message]
2014-11-11 8:29 ` martin rudalics
2014-11-11 14:26 ` Drew Adams
2014-11-11 18:31 ` martin rudalics
2014-11-11 19:01 ` Drew Adams
2014-11-11 21:04 ` Drew Adams
2014-11-13 5:12 ` Drew Adams
2014-11-13 7:44 ` martin rudalics
2014-11-13 15:23 ` Drew Adams
2014-11-13 16:28 ` martin rudalics
2014-11-13 16:56 ` Drew Adams
2014-11-13 18:47 ` martin rudalics
2014-11-13 19:21 ` Drew Adams
2014-11-14 11:37 ` martin rudalics
2014-11-14 15:11 ` Drew Adams
2014-11-14 16:38 ` martin rudalics
2014-11-14 17:09 ` Drew Adams
2014-11-14 17:39 ` martin rudalics
2014-11-14 17:47 ` Drew Adams
2014-11-14 18:10 ` martin rudalics
2014-11-14 18:28 ` Drew Adams
2014-11-14 18:33 ` martin rudalics
2014-11-14 18:44 ` Drew Adams
2014-11-14 19:08 ` martin rudalics
2014-11-14 21:21 ` Drew Adams
2014-11-15 11:24 ` martin rudalics
2014-11-15 14:40 ` Drew Adams
2014-11-16 11:36 ` martin rudalics
2014-11-16 16:20 ` Drew Adams
2014-11-16 17:36 ` martin rudalics
2014-11-16 20:06 ` Drew Adams
2014-11-17 9:29 ` martin rudalics
2014-11-17 14:29 ` Drew Adams
2014-12-25 19:30 ` martin rudalics
2014-11-11 22:16 ` Stefan Monnier
2014-11-11 23:10 ` Drew Adams
2014-11-12 1:49 ` Stefan Monnier
2014-11-12 2:36 ` Drew Adams
2014-11-12 4:11 ` Stefan Monnier
2014-11-12 7:18 ` Drew Adams
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=8e78202d-5ac0-4df5-8195-9849dd7509b7@default \
--to=drew.adams@oracle.com \
--cc=19012@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).