From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: from tb-ob20.topicbox.com (tb-ob20.topicbox.com [173.228.157.66]) by inbox.vuxu.org (Postfix) with ESMTP id C7584228D0 for ; Sat, 10 Aug 2024 23:32:44 +0200 (CEST) Received: from tb-mx1.topicbox.com (tb-mx1.nyi.icgroup.com [10.90.30.61]) by tb-ob20.topicbox.com (Postfix) with ESMTP id 45C9320B1C for ; Sat, 10 Aug 2024 17:32:43 -0400 (EDT) (envelope-from bounce.mM2e88845b92e7a51dca615ea9.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx1.topicbox.com (Postfix, from userid 1132) id 035661F73E66; Sat, 10 Aug 2024 17:32:43 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h=from:to :message-id:in-reply-to:references:date:mime-version :content-type:content-transfer-encoding:list-help:list-id :list-post:list-subscribe:reply-to:subject:list-unsubscribe; s= dkim-1; t=1723325562; x=1723411962; bh=e7LfRrJs5ciOHx3ZnIWcKSYch En7L7b3Ulcvg9ASlaI=; b=hN+vNgj7seqRa2zhqNjkiCcju3+CQS60jeTDtSt84 lnj+xXg+vHfjn/7wM08rOcMZbdt6LTIVkf3K4MGpCWwsoMYCPJX+kubZHYzazr7/ Jjl0R2isY6Ig0p0VzImn4VBMmgvgdV5k79l3s/HF7QNs05bxAJrRzGyrL3X98l8n S4= From: kalterdev@gmail.com To: 9fans <9fans@9fans.net> Message-Id: <17233255580.EbFBd.400013@composer.9fans.topicbox.com> In-Reply-To: <17233228160.1d47.67930@composer.9fans.topicbox.com> References: <17233228160.1d47.67930@composer.9fans.topicbox.com> Date: Sat, 10 Aug 2024 17:32:38 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=17233255581.9be7386cC.400013 Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 10cee0b0-5760-11ef-91e9-c256242d11b0 Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UMTExNDlmMWY5NDk1OTNmNS1NMmU4ODg0NWI5MmU3YTUxZGNhNjE1?= =?UTF-8?B?ZWE5Pg==?= List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> Subject: [9fans] Re: How do you deal with newlines (line feed, LF, \n) in filenames? List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:M2e88845b92e7a51dca615ea9:1:IkjMrh3xzaTwM8uZ0XalrAEudwugQMaBBmbti75V1mk --17233255581.9be7386cC.400013 Date: Sat, 10 Aug 2024 17:32:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi=C2=A0sirjofri, Thank you for your reply. I was referring to having newlines specifically i= n filenames. Sometimes it's not one's own fault that filenames have them. I wasn't really speaking about the way to represent a newline in rc, althou= gh thanks for details on that problem. My problem is to parse command outpu= t that has a newline in a filename. On my system, find(1) just prints the newline as is. So if the output looks= like this: a b It is actually possible that it means one "a\n" file, not file "a" and file= "b". Some commands, including ls(1) from plan9port, support quoting such files. = But then the problem is how to parse them. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T11149f1f949593f5-M2e888= 45b92e7a51dca615ea9 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --17233255581.9be7386cC.400013 Date: Sat, 10 Aug 2024 17:32:38 -0400 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi sirjofri,

=
Thank you for your reply. I was referring to having newlines specifica= lly in filenames. Sometimes it's not one's own fault that filenames= have them.

I wasn't really speaking about the way to repres= ent a newline in rc, although thanks for details on that problem. My proble= m is to parse command output that has a newline in a filename.
On my system, find(1) just prints the newline as is. So if t= he output looks like this:

a
b

It is actually possible that it means= one "a\n" file, not file "a" and file "b".

Some commands, including ls(1) from plan9po= rt, support quoting such files. But then the problem is how to parse them.<= br />
= --17233255581.9be7386cC.400013--