unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: gregory@heytings.org, emacs-devel@gnu.org, larsi@gnus.org
Subject: Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation
Date: Wed, 21 Sep 2022 15:53:59 +0300	[thread overview]
Message-ID: <83czbovqfs.fsf@gnu.org> (raw)
In-Reply-To: <87pmfpeyae.fsf@yahoo.com> (message from Po Lu on Wed, 21 Sep 2022 19:56:25 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: Gregory Heytings <gregory@heytings.org>,  emacs-devel@gnu.org,
>   larsi@gnus.org
> Date: Wed, 21 Sep 2022 19:56:25 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Yes.  I actually don't understand how can people use some other
> > policy, when moving focus to another frame or a different application
> > requires that you click on its window.  That basically means yopu
> > never work with more than one frame/window.
> 
> Interesting.
> 
> In the X world, we have mostly switched to "some other strategy",
> because that is what MS Windows does by default (and people are as a
> result used to.)

Bad habits of people who don't necessarily know something better is
possible.

On every new Windows machine where I need to do something for more
than 5 minutes, I always configure it to implicitly give focus to a
window where the mouse pointer is (but not raise it), because that's
the only way to type into one window while reading something in
another (unless you have a huge display where both windows can be
shown side by side).



  reply	other threads:[~2022-09-21 12:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166368675497.15121.15081377110947098460@vcs2.savannah.gnu.org>
     [not found] ` <20220920151239.61451C00871@vcs2.savannah.gnu.org>
2022-09-21  2:23   ` master 127ab231be 1/2: Attempt to clarify Input Focus documentation Po Lu
2022-09-21  9:14     ` Gregory Heytings
2022-09-21 10:41       ` Lars Ingebrigtsen
2022-09-21 10:54         ` Gregory Heytings
2022-09-21 10:51       ` Po Lu
2022-09-21 10:55         ` Lars Ingebrigtsen
2022-09-21 11:43           ` Po Lu
2022-09-21 10:58         ` Gregory Heytings
2022-09-21 11:51           ` Eli Zaretskii
2022-09-21 11:56             ` Po Lu
2022-09-21 12:53               ` Eli Zaretskii [this message]
2022-09-21 16:19                 ` [External] : " Drew Adams
2022-09-21 16:36                   ` Eli Zaretskii
2022-09-21 17:23                     ` Drew Adams
2022-09-21 17:39                       ` Eli Zaretskii
2022-09-21 21:37                         ` Drew Adams
2022-09-22  2:54                           ` Po Lu
2022-09-21 14:19             ` Gregory Heytings
2022-09-21 15:25               ` Andreas Schwab
2022-09-21 15:53                 ` Gregory Heytings
2022-09-22  4:29                   ` tomas
2022-09-22  6:53                     ` Robert Pluim
2022-09-22  5:42                   ` Po Lu
2022-09-21 12:07         ` Visuwesh
2022-09-21 15:06         ` tomas

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=83czbovqfs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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 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).