all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rswgnu@gmail.com
Cc: rudalics@gmx.at, monnier@iro.umontreal.ca, 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 19:26:30 +0200	[thread overview]
Message-ID: <83wp1mr3cp.fsf@gnu.org> (raw)
In-Reply-To: <CA+OMD9j5UM5Ke2iuGiyYW3UDkp3h=HjQfQZB1DDDRDdG+J7jFA@mail.gmail.com> (message from Robert Weiner on Sat, 16 Dec 2017 12:04:03 -0500)

> From: Robert Weiner <rsw@gnu.org>
> Date: Sat, 16 Dec 2017 12:04:03 -0500
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, martin rudalics <rudalics@gmx.at>, 
> 	emacs-devel <emacs-devel@gnu.org>
> 
> ​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?

There's a node "Input Focus" in the ELisp manual.  What is missing
from it to cover what you want?

In my scheme of Emacs-ware, there's no such thing as "redirecting
input to a window".  Input is redirected to a frame, and then the
selected window on that frame is usually the one that reacts to user
input (I say "usually' because some input, like mouse gestures, can
operate on n on-selected windows).

> 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.

Then perhaps the only stuff that's missing is some appropriately
worded index entries that lead to "Input Focus", and maybe also short
notes with cross-references elsewhere in the manual.



  parent reply	other threads:[~2017-12-16 17:26 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
2017-12-16 17:15                       ` Robert Weiner
2017-12-16 17:26                       ` Eli Zaretskii [this message]
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=83wp1mr3cp.fsf@gnu.org \
    --to=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.