From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Bug or inconsistency in cursor behaviour?
Date: Tue, 29 Oct 2024 18:41:21 +0100 [thread overview]
Message-ID: <CAFSF3XMCSzPyf99ZR_HGNgGn6W6Lwdw9ROL-3SS43kb0k8Ejbw@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XPEW_8bHRm6QqvMkYsrX8SzQL57XuSvA5krN1u+37nXuw@mail.gmail.com>
sorry. 60 years. (i'm not that old, so my memory is a bit fuzzy).
On Tue, Oct 29, 2024 at 6:40 PM hiro <23hiro@gmail.com> wrote:
>
> your fingers are correct to reject this cybernetic failure. proper
> thought into how to improve this sad resulting human intellect has
> ceased 40 years ago.
>
> On Tue, Oct 29, 2024 at 4:18 PM Scott Flowers <flowerss@cranky.ca> wrote:
> >
> > I am declaring my fingers' inability to get used to the existing behaviour in rio and acme to be a human software bug, and I'm keeping my patch on my machines. As Sigrid once said, "it's your system, do what you want."
> >
> > Scott
> >
> > On Tue, 29 Oct 2024, at 03:59, hiro wrote:
> > > > There is a logical argument to the Plan 9 behavior: First, the cursor
> > > > disappears when you make a selection because the cursor *IS* the
> > > > selection.
> > >
> > > may i point out that this is the perceived behavior on windows due to
> > > common vision limitations? the designers were aware of this visual
> > > difficulty or they wouldn't have made the cursor blink. yet the edge
> > > becomes nearly-undetectable in the edge-case of selection. who knows
> > > if they ever noticed the lack of intuition in this pattern?
> > >
> > > regardless there remains a logic i feel some plan9 folks might not
> > > know about: the blinking cursor helps suggest whether selection will
> > > be added to or removed from via keyboard actions
> > > (shift-left/shift-right), a feature that does not exist on plan9.
> > > otherwise it exclusively confuses the well-sighted. at least in some
> > > applications: i'm not sure if rob pike managed to infiltrate the
> > > mozilla headquarters and forced them to remove that cursor, but it's
> > > missing in my firefox.
> > >
next prev parent reply other threads:[~2024-10-29 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 20:19 flowerss
2024-10-28 22:49 ` Scott Flowers
2024-10-28 22:59 ` Scott Flowers
2024-10-28 23:04 ` Scott Flowers
2024-10-28 23:45 ` Thaddeus Woskowiak
2024-10-29 0:35 ` Scott Flowers
2024-10-29 9:59 ` hiro
2024-10-29 15:16 ` Scott Flowers
2024-10-29 17:40 ` hiro
2024-10-29 17:41 ` hiro [this message]
2024-10-29 1:40 ` ori
2024-10-29 3:31 ` Scott Flowers
2024-10-29 4:32 ` umbraticus
2024-10-29 9:26 ` hiro
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=CAFSF3XMCSzPyf99ZR_HGNgGn6W6Lwdw9ROL-3SS43kb0k8Ejbw@mail.gmail.com \
--to=23hiro@gmail.com \
--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).