From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 9545 invoked from network); 5 Nov 2021 22:14:06 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 5 Nov 2021 22:14:06 -0000
Received: from seninha.org ([45.76.8.186]) by 4ess; Fri Nov  5 16:23:17 -0400 2021
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=20211006; bh=UFBqMcNwaUR
	iJY2jBZ9fScSVbSkoP6gvRspa8w1DEeo=; h=in-reply-to:references:subject:
	to:from:date; d=seninha.org; b=NoIGssileLqksyQP/FHtuZi0woKCVWngQFuhqDv
	DF7abOrPo1Tkgi2uFsin3pxVfiwR2X6ooYwdvLbWth7R4HkIKUgfYvNLJzVqyqS2NQumX7
	vgNfYjtB5GLMkMUVyMiASN1WGr4IywNivnQFmPbqMIsHsMypJzl3OFaXY3SIUfV6iU7BhH
	6tBTCd0J41wwr5DUF7f87eFSCS2VmD4ZKOxisDNh51cd3wiFU7plOgBxd6EHrhcV+BeJEc
	ccYIMBvvN0sckcg9715M6nNwRTIieDQNZspO2rOhESYd+OGrfIrGy7/oVQGVPJuRyVBuCc
	BKd9XzBSTQITHpn6gWTmfsA==
Received: from localhost (b3d611d6.virtua.com.br [179.214.17.214])
	by mail.seninha.org (OpenSMTPD) with ESMTPSA id a708dbc9 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO)
	for <9front@9front.org>;
	Fri, 5 Nov 2021 17:23:08 -0300 (-03)
Date: Fri, 5 Nov 2021 17:22:58 -0300
From: Lucas de Sena <lucas@seninha.org>
To: 9front@9front.org
Message-ID: <YYWSol4WEvZqoziO@thinkbsd>
References: <560B46E39B1DC0F1E9D0BCDE6ABE3B56@prosimetrum.com>
 <8293348E29722D25668BB3B02D1759F5@9lab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8293348E29722D25668BB3B02D1759F5@9lab.org>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: basic responsive session storage package extension 
Subject: Re: [9front] [PATCH] rio(1): add triple-clicking and shift-up/down
Reply-To: 9front@9front.org
Precedence: bulk

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