9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Lucas de Sena <lucas@seninha.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
Date: Fri, 5 Nov 2021 17:22:58 -0300	[thread overview]
Message-ID: <YYWSol4WEvZqoziO@thinkbsd> (raw)
In-Reply-To: <8293348E29722D25668BB3B02D1759F5@9lab.org>

What about the following?

> A third click can be done after a double-clicking
> that is not inside a matched delimited-pair
> and that selects either nothing or an alphanumeric word;
> it selects non-whitespace characters around the original selection
> and the original selection itself.

Kinda verbose, but I think it's correct.

The manual is clear that a selection can be a null string (in which case
the selection is indicated by a hairline cursor between two characters).
So I expanded my sentence to include that the double-clicking before the
third one can be either a null string selection, or an alphanumeric word
selection.  If I understood correctly those are the cases when the third
click makes the original selection be bound by the whitespace around it.

This sentence also covers the case of triple-clicking between delimiters
with no text inside them, such as ().

The "non-whitespace" can be replaced by "non-blank". I don't know what's
the semantical difference of those two expressions in Plan 9, nor how it
applies to the triple-clicking selection.

Regarding the shift-up/down.  It is a rio feature.  So I think it should
be documented in the manual (even if considered a bad practice by some).

      reply	other threads:[~2021-11-05 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 22:49 Lucas de Sena
2021-11-04 23:22 ` umbraticus
2021-11-04 23:34   ` hiro
2021-11-05  0:22     ` umbraticus
2021-11-05  0:39       ` sl
2021-11-05  0:40   ` igor
2021-11-05 20:22     ` Lucas de Sena [this message]

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=YYWSol4WEvZqoziO@thinkbsd \
    --to=lucas@seninha.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).