9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Bug or inconsistency in cursor behaviour?
Date: Mon, 28 Oct 2024 21:40:33 -0400	[thread overview]
Message-ID: <532996A74BEC9105F656EF9C83F7B5C3@eigenstate.org> (raw)
In-Reply-To: <588564A0F1AB6824ED04551648A54C37@cranky.ca>

Quoth flowerss@cranky.ca:
> I have noticed an odd behaviour when using the arrow keys when text is selected in 9front, and I'm wondering if it's a bug, multiple bugs, or just the way things work.
> 
> If I have a string of text in a shell or acme, and I select one or more characters with the mouse, and then use the right arrow key, the text gets deselected, and the cursor moves one character past the right end of the selected text. If I use the left arrow key, the cursor moves to one character to the left of the previously selected text. It feels like the resultin position of the cursor has gone one character too far left or right.

This is intentional, just a different way that things work. An arrow just moves
the dot.

> In sam, this behaviour is different. If I select text in sam, and then hit the left arrow key, the cursor moves one character to the left of the initially selected text, and if I hit the right arrow key, the cursor moves to the right of the first character of the previously selected text. This also seems odd.
>

This one, I'd call a bug.
 
> In Windows, MacOS and all the Linux graphical text manipulation apps I have tried, if you select text and then hit the left arrow, the cursor moves to the beginning of the selection, and the right arrow moves to the end of the selection. This feels like the more appropriate behaviour to me. Am I out to lunch?
> 
> Thanks,
> 
> Scott


  parent reply	other threads:[~2024-10-29  1:43 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
2024-10-29  1:40 ` ori [this message]
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=532996A74BEC9105F656EF9C83F7B5C3@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).