unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 12:04:03 -0500	[thread overview]
Message-ID: <CA+OMD9j5UM5Ke2iuGiyYW3UDkp3h=HjQfQZB1DDDRDdG+J7jFA@mail.gmail.com> (raw)
In-Reply-To: <834loqskkw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]

On Sat, Dec 16, 2017 at 11:29 AM, Eli Zaretskii <eliz@gnu.org> wrote:

>
> > ​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?
>
> Yes.  You are proposing to add text about a completely unrelated
> aspect of Emacs.  Selecting a window has nothing to do with focus


​The main question I am trying to address is how to tell an Elisp programmer
how to redirect user input to an arbitrary window.  Whether or not we have
a specific name for this redirection, where user input goes changes when
select-window is called within the selected frame.  So there is input focus
which is frame-related but there is also window-related input redirection.
My argument is that there needs to be one place to look to understand
that.

Maybe select-window is not the place, it just seems that programmers
focused on
handling windows would naturally look there.

How and where would you explain this?  Can you explain how to do it in a few
sentences?  If yes, then let's add it somewhere and make it easy to find.
If not, then maybe a simplifying function would be justified.

I read through parts of the Elisp manual.  The section on Windows does not
explain
how to redirect user input ot an arbitrary window.  The top-level on Frames
does
not either.  It is not until I get to the section on Input Focus that I get
any
helpful information on this and that section refers only to frames, not
selected
windows.

So my thought is that where interactive user input goes is broader than
input focus,
is connected to what window is selected, and should be explained in one
place in
a succinct manner that is easily findable when looking up windows or frames.

Bob

[-- Attachment #2: Type: text/html, Size: 4758 bytes --]

  reply	other threads:[~2017-12-16 17:04 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
2017-12-16 16:29                   ` Eli Zaretskii
2017-12-16 17:04                     ` Robert Weiner [this message]
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

  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='CA+OMD9j5UM5Ke2iuGiyYW3UDkp3h=HjQfQZB1DDDRDdG+J7jFA@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 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).