unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation
Date: Thu, 22 Sep 2022 06:29:56 +0200	[thread overview]
Message-ID: <YyvkxEq+wuWyHysh@tuxteam.de> (raw)
In-Reply-To: <2d1b683c22a58e9509e6@heytings.org>

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

On Wed, Sep 21, 2022 at 03:53:08PM +0000, Gregory Heytings wrote:
> 
> > > The focus-follows-mouse policy is indeed superior for advanced
> > > users, but I think it must be admitted that it isn't appropriate for
> > > regular users [...]

I wouldn't put that in a hierarchy like that. It's just how accustomed
the user is to a set of UI conventions. Besides, that makes your
hypothetical "regular user" identical with the "windows user", which
is a sneaky way of cementing Microsoft's supremacy. Don't let us do
their job for them. They are unfortunately good enough at it without
us helping :)

One could argue that "modern Windows" with its several layers of
UI "languages" is only for "advanced users". You have to know that
the first click on an "old" Windows app does nothing but bring
the focus to that one (e.g. Terminal), whereas a "modern" app (a
browser for example) goes wild on the first click. For me, very
much advanced indeed (I keep looking for harmless places on some
wacky web page to click on to be able to type there).

> > Though this is the raise-on-focus option, which is independent from
> > focus-follows-mouse vs. click-to-focus.

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)
> 
> 2. focus-follows-mouse (traditional behavior on X11)
> 
> 2.1. raise-on-click (default)
> 
> 2.2. raise-on-focus

Theoretically, of course, one might conceive click-to-focus /without/
raise-on-focus. But I haven't seen that for a long time.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-09-22  4:29 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 [this message]
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=YyvkxEq+wuWyHysh@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    /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).