<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi, sorry for the delayed response; I had to confirm I could share it, and doofus me tried to do this on a Friday afternoon.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Anyway, I'm attaching the patch. I'm not thrilled by the <code>goto</code> in the argument processing, but I was worried about tracing side effects if I pulled things out to another function. Feel free to adjust of course.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Evan</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Christos Zoulas <christos@zoulas.com><br>
<b>Sent:</b> Friday, June 7, 2024 5:28 PM<br>
<b>To:</b> Evan Driscoll <edriscoll@codesecure.com><br>
<b>Cc:</b> file@astron.com <file@astron.com><br>
<b>Subject:</b> [External] - Re: [File] Feature request / patch offer: What about a `--files-from0` option?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">[You don't often get email from christos@zoulas.com. Learn why this is important at
<a href="https://aka.ms/LearnAboutSenderIdentification">https://aka.ms/LearnAboutSenderIdentification</a> ]<br>
<br>
CAUTION: External Email<br>
<br>
<br>
Sure, just send a patch. No copyright assignment needed...<br>
<br>
christos<br>
<br>
> On Jun 7, 2024, at 4:52 PM, Evan Driscoll <edriscoll@codesecure.com> wrote:<br>
><br>
> The `--0` option to `file` provides a nice way to get perfect parsing of results that include unfortunate file names.<br>
><br>
> However, there's not an analogue on the input side for providing filenames via a file, a la `--files-from`. Would it be possible to add an option, say `--files-from0`, that functions like `--files-from` except that the filenames are `\0` separated instead
of newline-separated?<br>
><br>
> I've put my money where my mouth is a bit, and implemented this locally; with some light testing only, it seems to work. I *believe* I can offer this patch. Is it of interest? What are your contribution requirements in terms of copyright assignment and whatnot?<br>
><br>
> Thanks,<br>
> Evan Driscoll<br>
> ________________________________<br>
> The information contained in this e-mail and any attachments from CodeSecure, Inc may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient,
any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.<br>
> --<br>
> File mailing list<br>
> File@astron.com<br>
> <a href="https://mailman.astron.com/mailman/listinfo/file">https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.astron.com%2Fmailman%2Flistinfo%2Ffile&data=05%7C02%7Cedriscoll%40codesecure.com%7Cde26b67b514146ba79fe08dc87413f45%7C3b03d731b2154ba7baac94f143da2377%7C0%7C0%7C638533962182457700%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C60000%7C%7C%7C&sdata=LqY9NHE64v09ga2aj6HfoZW4rnA4JQA8V4U1c%2FHg4ss%3D&reserved=0</a><br>
><br>
> --<br>
> This message has been 'sanitized'. This means that potentially<br>
> dangerous content has been rewritten or removed. The following<br>
> log describes which actions were taken.<br>
><br>
> Sanitizer (start="1717799244"):<br>
> Split unusually long word(s) in header.<br>
> SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):<br>
> Match (names="unnamed.txt", rule="9"):<br>
> Enforced policy: accept<br>
><br>
> Total modifications so far: 1<br>
><br>
><br>
> Anomy 0.0.0 : Sanitizer.pm<br>
> $Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $<br>
><br>
<br>
</div>
</span></font></div>
<div style="font-size:8pt; font-family: 'Calibri',sans-serif;">
<hr>
The information contained in this e-mail and any attachments from CodeSecure, Inc may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient,
any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.</div>
</body>
</html>