From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id 85C2020281
	for <ml@inbox.vuxu.org>; Wed,  6 Nov 2024 05:58:48 +0100 (CET)
Received: from asquith.prosimetrum.com ([125.236.209.157]) by 9front; Tue Nov  5 23:57:49 -0500 2024
Message-ID: <A3223ED45264DADD8B67CCBC77DF815D@prosimetrum.com>
Date: Wed, 06 Nov 2024 17:57:50 +1300
From: umbraticus@prosimetrum.com
To: 9front@9front.org
In-Reply-To: <32ERPD9FSEHN0.2PR9UYWTR5B74@canaglie.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: abstract reduce/map content-driven controller 
Subject: Re: [9front] plumbing with spaces
Reply-To: 9front@9front.org
Precedence: bulk

It's not really the plumber's fault; rather it's how the
programs at either end cope. I do think it would be
nice if you could select a line in rio by double-clicking
then plumb: sadly the newline messes things up, so
one must resort to surrounding spacey plumb strings
with brackets or braces or quotes or whatever to avoid
precision sweeping. Both sam and ed cope with my
'test file with spaces' per the below rule. I pass no
comment on any other editor.

data matches test.*
arg isfile $data
plumb start window sam ''''$file''''

umbraticus