9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Eckard Brauer <eckard.brauer@gmx.de>
To: 9front@9front.org
Subject: Re: [9front] PATCH: click-to-focus in fgui
Date: Thu, 12 Aug 2021 16:36:26 +0200	[thread overview]
Message-ID: <20210812163626.63c3fb64@gmx.de> (raw)
In-Reply-To: <CAFSF3XN_FLiDXaR7Nj1gUyUSrhkn4kyUDH+kEUF6Rw69j-W2hg@mail.gmail.com>

> > I guess I really want the focus following my eyes.  
> 
> no you really don't

I'd rather want focus to follow the mouse lazily as long as there's a
possibility to switch/cycle windows with the keyboard. So I usually
don't have an idea where the mouse pointer is left and do most of the
work with the keyboard. Mouse is only used for selecting/pasting.

But that's not much approved (and maybe possible at all) on Plan 9.
IMHO it'd be best to leave the user to choose, if it's with a path or
compile time #ifdefs, it would be fine for me.


-- 
Corona? Ich desinfiziere regelmäßig mit Bier. 
What Corona? I regularly disinfect with beer.

  reply	other threads:[~2021-08-13  5:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 22:59 Silas McCroskey
2021-08-10 14:19 ` ori
2021-08-11  5:28   ` rgl
2021-08-11 20:49     ` Philip Silva
2021-08-11 21:09       ` Steve Simon
2021-08-11 22:37       ` Xiao-Yong Jin
2021-08-12  9:05         ` hiro
2021-08-12 14:36           ` Eckard Brauer [this message]
2021-08-13  6:44             ` unobe
2021-08-13  7:10               ` hiro
2021-08-14 10:20                 ` Eckard Brauer
2021-08-14 13:09                   ` qwx
2021-08-14 15:03                     ` Stuart Morrow
2021-08-14 13:17                   ` José Miguel Sánchez García
2021-08-14 20:57                     ` Patch-keeping (Was Re: [9front] PATCH: click-to-focus in fgui) unobe
2021-08-14 15:04                   ` [9front] PATCH: click-to-focus in fgui Stuart Morrow
2021-08-14 18:08                   ` hiro
2021-08-14 21:43                     ` unobe
2021-08-15  6:47                       ` hiro
2021-08-14 21:46                   ` unobe
2021-08-15 13:36                     ` Eckard Brauer
2021-08-15 19:16                       ` hiro
2021-08-15 17:31                   ` kvik
2021-08-15 18:34                     ` Kurt H Maier
2021-08-15 18:48                     ` Stanley Lieber
2021-08-15 20:18                       ` Eckard Brauer
2021-08-15 22:35                         ` Stanley Lieber
2021-08-16  5:14                           ` Stanley Lieber
2021-08-16 15:46                             ` Skylar Bleed
2021-08-15 19:03                     ` hiro
2021-08-16 16:40                       ` kvik
2021-08-16 19:25                         ` Stuart Morrow
2021-08-16 19:40                           ` Kurt H Maier
2021-08-17  2:05                             ` Stanley Lieber
2021-08-16 20:04                         ` hiro
2021-08-16 20:13                         ` hiro
2021-08-17  1:10                           ` Xiao-Yong Jin
2021-08-17  8:11                             ` hiro
2021-08-12  0:12       ` hiro
2021-08-15  4:29       ` ori
2021-08-16 19:40 ` ori

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=20210812163626.63c3fb64@gmx.de \
    --to=eckard.brauer@gmx.de \
    --cc=9front@9front.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.
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 NNTP newsgroup(s).