From: Robert Weiner <rsw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Suggestion: Add discussion of input focus handling to select-window; add select-frame-window
Date: Sat, 16 Dec 2017 11:21:56 -0500 [thread overview]
Message-ID: <CA+OMD9g_pfUFUZ7u2v0QepsdxDqTejTTvp8e7XrajsjgdTrFeg@mail.gmail.com> (raw)
In-Reply-To: <CA+OMD9hPXxfhVQ4UuYFMaKDoW6k2DbkN--1oajQ4exV=ef++4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Thu, Dec 14, 2017 at 10:01 AM, Robert Weiner <rsw@gnu.org> wrote:
> On Wed, Dec 13, 2017 at 10:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>
>> My misunderstanding, sorry.
>>
>> But if the issue is documentation, why not show a proposed patch?
>>
>
> I did with this suggested addition to select-window's doc string:
>
> "Although this selects the window's frame, it does not alter the
> frame's position in the window stack (see `raise-frame') nor does
> it direct input focus to that frame. To do both of those at once,
> see `select-frame-set-input-focus'.
>
I still think this is a clear and modest proposal. select-window already
mentions frames so I don't see an issue with cross-referencing more
frame-related
behavior to make the needs clear with one additional sentence. Are you guys
still against this given the further explanations?
Bob
[-- Attachment #2: Type: text/html, Size: 3160 bytes --]
next prev parent reply other threads:[~2017-12-16 16:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 15:39 Suggestion: Add discussion of input focus handling to select-window; add select-frame-window Robert Weiner
2017-12-12 18:13 ` Robert Weiner
2017-12-12 18:49 ` Robert Weiner
2017-12-12 20:40 ` Stefan Monnier
2017-12-12 21:29 ` Robert Weiner
2017-12-12 21:57 ` Stefan Monnier
2017-12-12 20:37 ` Stefan Monnier
2017-12-12 21:19 ` Robert Weiner
2017-12-13 8:49 ` martin rudalics
2017-12-13 13:37 ` Stefan Monnier
2017-12-13 14:37 ` Robert Weiner
2017-12-13 19:29 ` martin rudalics
2017-12-13 20:30 ` Eli Zaretskii
2017-12-13 22:10 ` Stefan Monnier
2017-12-14 3:33 ` Eli Zaretskii
2017-12-14 15:01 ` Robert Weiner
2017-12-14 20:09 ` Eli Zaretskii
2017-12-14 23:43 ` Robert Weiner
2017-12-15 1:42 ` Stefan Monnier
2017-12-16 16:11 ` Robert Weiner
2017-12-16 16:42 ` Eli Zaretskii
2017-12-16 17:23 ` Robert Weiner
2017-12-16 16:27 ` Robert Weiner
2017-12-16 16:21 ` Robert Weiner [this message]
2017-12-16 16:29 ` Eli Zaretskii
2017-12-16 17:04 ` Robert Weiner
2017-12-16 17:15 ` Robert Weiner
2017-12-16 17:26 ` Eli Zaretskii
2017-12-16 18:16 ` Robert Weiner
2017-12-16 18:41 ` Eli Zaretskii
2017-12-16 19:18 ` Robert Weiner
2017-12-16 19:56 ` Eli Zaretskii
2017-12-16 20:52 ` Robert Weiner
2017-12-22 10:19 ` Eli Zaretskii
2017-12-16 22:44 ` Robert Weiner
2017-12-13 14:51 ` Robert Weiner
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=CA+OMD9g_pfUFUZ7u2v0QepsdxDqTejTTvp8e7XrajsjgdTrFeg@mail.gmail.com \
--to=rsw@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rswgnu@gmail.com \
--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 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.