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.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18317 invoked from network); 26 Aug 2023 18:06:14 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 Aug 2023 18:06:14 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Sat Aug 26 14:00:11 -0400 2023 Received: from abbatoir (pool-108-27-53-161.nycmny.fios.verizon.net [108.27.53.161]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id c8cdf9e8 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO); Sat, 26 Aug 2023 11:00:09 -0700 (PDT) Message-ID: To: 9front@9front.org CC: k0ga@shike2.com Date: Sat, 26 Aug 2023 14:00:07 -0400 From: ori@eigenstate.org In-Reply-To: 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: polling-oriented singleton cloud frontend Subject: Re: [9front] sed: fix moving '^' match Reply-To: 9front@9front.org Precedence: bulk Quoth hiro <23hiro@gmail.com>: > i disagree, i can interprete sed(1) to allow exactly this feature you expect changes to the line to be visible within a single search/replace operation? can you explain why?