From: Robert Pluim <rpluim@gmail.com>
To: <tomas@tuxteam.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation
Date: Thu, 22 Sep 2022 08:53:58 +0200 [thread overview]
Message-ID: <87zgerc321.fsf@gmail.com> (raw)
In-Reply-To: <YyvkxEq+wuWyHysh@tuxteam.de> (tomas@tuxteam.de's message of "Thu, 22 Sep 2022 06:29:56 +0200")
>>>>> On Thu, 22 Sep 2022 06:29:56 +0200, <tomas@tuxteam.de> said:
tomas> One could argue that "modern Windows" with its several layers of
tomas> UI "languages" is only for "advanced users". You have to know that
tomas> the first click on an "old" Windows app does nothing but bring
tomas> the focus to that one (e.g. Terminal), whereas a "modern" app (a
tomas> browser for example) goes wild on the first click. For me, very
tomas> much advanced indeed (I keep looking for harmless places on some
tomas> wacky web page to click on to be able to type there).
Web browsers are particularly annoying here: clicking in the url bar
will select the entire url, making you click again to place the cursor
where you want to make the edit (does that make me an "advanced user"?
😀)
>> > Though this is the raise-on-focus option, which is independent from
>> > focus-follows-mouse vs. click-to-focus.
tomas> You are right, Andreas -- I do appreciate both.
>> It depends on how you look at it, I guess. I would rather present it as a
>> sub-option:
>>
>> 1. click-to-focus (default behavior on Windows and macOS)
>>
macOS these days is not strictly click-to-focus, it has hybrid
focus-under-mouse (which actually generally does the right thing,
except when you have two overlapping windows).
Robert
--
next prev parent reply other threads:[~2022-09-22 6: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
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 [this message]
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=87zgerc321.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/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).