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 B8BE3236A6 for ; Thu, 7 Nov 2024 09:53:38 +0100 (CET) Received: from asquith.prosimetrum.com ([125.236.209.157]) by 9front; Thu Nov 7 03:52:40 -0500 2024 Message-ID: Date: Thu, 07 Nov 2024 21:52:42 +1300 From: umbraticus@prosimetrum.com To: 9front@9front.org In-Reply-To: <8DF479DCD404E657DA8A64B2232A9BF7@prosimetrum.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: optimized event-oriented cache Subject: Re: [9front] plumbing with spaces Reply-To: 9front@9front.org Precedence: bulk hahaha I exited hold mode on my email and immediately came up with a plumb rule that succeeds in matching a newline: data matches '[ - ]' plumb start echo boo That's a range from \x9 to \xb. Indeed, I see boo on my console, so everything else plays nice. Adding support for \n seems like a decent convenience. umbraticus