9front - general discussion about 9front
 help / color / mirror / Atom feed
* [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
@ 2021-11-04 22:49 Lucas de Sena
  2021-11-04 23:22 ` umbraticus
  0 siblings, 1 reply; 7+ messages in thread
From: Lucas de Sena @ 2021-11-04 22:49 UTC (permalink / raw)
  To: 9front

---
 sys/man/1/rio | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sys/man/1/rio b/sys/man/1/rio
index 4f42d4f61..7808ba3e2 100644
--- a/sys/man/1/rio
+++ b/sys/man/1/rio
@@ -305,6 +305,8 @@ on the right, it selects all text within
 the pair; at the beginning
 or end of a line, it selects the line; within or at the edge of an alphanumeric word,
 it selects the word.
+A third click can be done right after a double-clicking that selects an alphanumeric word,
+it selects the word itself and the non-whitespace characters around it.
 .PP
 Characters typed on the keyboard replace the selected text;
 if this text is not empty, it is placed in a
@@ -414,6 +416,7 @@ scrolls forward
 half a window, and page up or up-arrow scrolls back.
 Typing the home key scrolls to the top of the window; typing the end key scrolls
 to the bottom.
+The shift key pressed along with the up-arrow (down-arrow) scrolls backward (forward) one line.
 .PP
 The DEL character sends an
 .L interrupt
-- 
2.33.0


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-04 22:49 [9front] [PATCH] rio(1): add triple-clicking and shift-up/down Lucas de Sena
@ 2021-11-04 23:22 ` umbraticus
  2021-11-04 23:34   ` hiro
  2021-11-05  0:40   ` igor
  0 siblings, 2 replies; 7+ messages in thread
From: umbraticus @ 2021-11-04 23:22 UTC (permalink / raw)
  To: 9front

+A third click can be done right after a double-clicking that selects an alphanumeric word,
+it selects the word itself and the non-whitespace characters around it.

Sounds complicated and maybe slightly wrong
(triple-click on +.+-+/+, for example); what about just:

Triple-clicking makes a selection bounded by whitespace.

For shift, I think this section should be rephrased instead:

Also, a page down
or down-arrow
scrolls forward
half a window, and page up or up-arrow scrolls back.

and while we're at it we can correct it to ⅓, ⅔, and 1 line.

umbraticus

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-04 23:22 ` umbraticus
@ 2021-11-04 23:34   ` hiro
  2021-11-05  0:22     ` umbraticus
  2021-11-05  0:40   ` igor
  1 sibling, 1 reply; 7+ messages in thread
From: hiro @ 2021-11-04 23:34 UTC (permalink / raw)
  To: 9front

so now we get to document these errors, too?
why would anybody need to scroll by single lines. this feature
suggests useless usage habits, that nobody should have in the first
place.

On 11/5/21, umbraticus@prosimetrum.com <umbraticus@prosimetrum.com> wrote:
> +A third click can be done right after a double-clicking that selects an
> alphanumeric word,
> +it selects the word itself and the non-whitespace characters around it.
>
> Sounds complicated and maybe slightly wrong
> (triple-click on +.+-+/+, for example); what about just:
>
> Triple-clicking makes a selection bounded by whitespace.
>
> For shift, I think this section should be rephrased instead:
>
> Also, a page down
> or down-arrow
> scrolls forward
> half a window, and page up or up-arrow scrolls back.
>
> and while we're at it we can correct it to ⅓, ⅔, and 1 line.
>
> umbraticus
>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-04 23:34   ` hiro
@ 2021-11-05  0:22     ` umbraticus
  2021-11-05  0:39       ` sl
  0 siblings, 1 reply; 7+ messages in thread
From: umbraticus @ 2021-11-05  0:22 UTC (permalink / raw)
  To: 9front

> this feature suggests useless usage habits

blame sl

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-05  0:22     ` umbraticus
@ 2021-11-05  0:39       ` sl
  0 siblings, 0 replies; 7+ messages in thread
From: sl @ 2021-11-05  0:39 UTC (permalink / raw)
  To: 9front

>> this feature suggests useless usage habits
> 
> blame sl

oh, he did.

sl

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-04 23:22 ` umbraticus
  2021-11-04 23:34   ` hiro
@ 2021-11-05  0:40   ` igor
  2021-11-05 20:22     ` Lucas de Sena
  1 sibling, 1 reply; 7+ messages in thread
From: igor @ 2021-11-05  0:40 UTC (permalink / raw)
  To: 9front; +Cc: umbraticus

Quoth umbraticus@prosimetrum.com:
> +A third click can be done right after a double-clicking that selects an alphanumeric word,
> +it selects the word itself and the non-whitespace characters around it.
> 
> Sounds complicated and maybe slightly wrong
> (triple-click on +.+-+/+, for example); what about just:
> 
> Triple-clicking makes a selection bounded by whitespace.

While the above definition is simple and therefore appealing,
it is not entirely correct. Try triple clicking on `middle`:

• left(middle)right

…that will indeed make a selection bounded by whitespace.

Now try the same for `m` below:

• left(m)right

The selection after triple clicking on `m` is bounded by `(` and `)`,
not by whitespace. Unless I am missing something obvious it looks like
the logic for the triple click selection is not working as expected in
this case…

Cheers,
Igor


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
  2021-11-05  0:40   ` igor
@ 2021-11-05 20:22     ` Lucas de Sena
  0 siblings, 0 replies; 7+ messages in thread
From: Lucas de Sena @ 2021-11-05 20:22 UTC (permalink / raw)
  To: 9front

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).

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-11-05 22:14 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-04 22:49 [9front] [PATCH] rio(1): add triple-clicking and shift-up/down 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 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).