From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 19012@debbugs.gnu.org
Subject: bug#19012: 25.0.50; `help-window-select'
Date: Thu, 13 Nov 2014 19:47:49 +0100 [thread overview]
Message-ID: <5464FCD5.6070201@gmx.at> (raw)
In-Reply-To: <ab8b3164-4c8d-4fd0-a835-e401ee08c3d7@default>
>> So you want `raise-frame' to not select the frame and `with-help-
>> window' select the frame? Any preferences who should win that game?
>
> There is no game.
>
> 1. `raise-frame' should not focus the frame (or unfocus it), unless
> `w32-grab-focus-on-raise' is non-nil (or unless there is also some
> other, similar option that makes `raise-frame' grab the focus).
> And as far as I can tell, that is the case: it does not.
IIUC the default behavior on Windows is that when you raise a frame,
that frame gets focus as well. So if you set `w32-grab-focus-on-raise'
to nil, Emacs has to explicitly tell Windows to unfocus the frame.
> But even if it did, that should be irrelevant to what
> `help-select-window' does (*this* bug).
What is "*this* bug"? You attribute a behavior you observe to a
variable that does not and cannot control that behavior.
> `raise-frame' is punctual.
I have no idea what you mean here.
> The scope and effect of `help-select-window' are controlled by
> `with-help-window' (according to you, whom I believe; I'm no expert
> on that, and that is not documented, AFAICT).
Scope and effect of `help-window-select' end where `with-help-window'
exits.
> 2. `help-window-select' = `t' (within `with-help-window', at least)
> should select the help window. (Likewise, for a value of `other',
> unless the selected window is alone on the help-window's frame.)
>
> This is all specified by the doc (except the connection between
> `help-window-select' and `with-help-window'). And there is no
> contradiction between #1 and #2. `help-window-select' has nothing
> to do with `w32-grab-focus-on-raise' and nothing to do with
> `raise-frame' (at least according to its spec/doc). And it *should*
> have nothing to do with them.
If `help-window-select' is t, `with-help-window' selects the frame
unconditionally.
> Whether `raise-frame' focuses the frame or not should be irrelevant
> to the behavior imposed by `help-window-select'. It is (according
> to you) `with-help-window' that controls the scope of the effect
> of `help-window-select'. It is `with-help-window' that should
> ensure that `help-window-select' has the effect it claims to have
> when `with-help-window' is finished.
Doesn't it?
>> > It is you who stated what I should expect from the behavior
>> > of `help-select-window', provided the context is
>> > `with-help-window'. *You* stated that it is a bug if the
>> > window is not selected.
>>
>> So far you did not provide any evidence that the window is not
>> selected.
>
> Sure I did.
You didn't even care to go through this with a debugger. What kind of
evidence is that?
> I said that it does not have the input focus. Type
> text and it goes to the window where you hit `C-h v'. What's more,
> the frame border highlighting shows that the frame is not focused.
This does not contradict that `with-help-window' selected the window.
> You seem to be in denial, for some reason. Believe me, the
> *Help*-selecting effect of non-nil `help-select-window' disappears
> if `w32-grab-focus-on-raise' is nil.
I never doubted that. But it seems to me that you don't want to care
how a nil value for `w32-grab-focus-on-raise' gets processed. There is
absolutely nothing `with-help-window' or any Elisp code can do there.
> It should not disappear. `w32-grab-focus-on-raise' should affect
> only `raise-frame'. And `help-window-select' & `with-help-window'
> should not be affected by whether there is a call to `raise-frame'
> or what such a call might do wrt frame focus.
You can't have both - select the frame and unfocus it.
martin
next prev parent reply other threads:[~2014-11-13 18:47 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5464FCD5.6070201@gmx.at \
--to=rudalics@gmx.at \
--cc=19012@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.