On Sat, Dec 16, 2017 at 12:26 PM, Eli Zaretskii <eliz@gnu.org> wrote:

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


​When the user selects another window within the selected frame
or a select-window is done on the selected frame, user input
(typing) and programmatic input (insert) shifts from the prior
window to the new window.  No frame change has occurred yet
where user input like self-inserting characters goes is different.
How can this not be part of your Emacs model?

​​
>   Input is redirected to a frame, and then t
> ​​
> ​​
> he
> ​​
>
> ​​
> 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).
>
​​
​
​Some concept other than input focus is sending those inputs to the
selected window (maybe we limit discussion to keyboard inputs for now).
Maybe it could have a name and be described.
​

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

​​
Frame-level input focus is insufficient to describe the window to which
keyboard input goes in all cases.  It requires a combination of set input
focus and select-window, right?  Plus, if we want to see any changes in
buffer-to-window mappings during the course of a function, we must invoke
redisplay.  It is the description of the interrelations of these things that
is not described in a single place anywhere, especially with code samples,
making it difficult for programmers to see what must be done.

Bob