From: me@shurizzle.dev
To: 9front@9front.org
Subject: Re: [9front] [PATCH] feat(grep): add -H flag
Date: Wed, 26 Jun 2024 14:08:43 +0000 [thread overview]
Message-ID: <wjcgdmoxi535qmfv3mdmtrrlbfeutfj3o5gcf244jxgyqt6rv4@xhsiqs2il2zq> (raw)
In-Reply-To: <B458772E9293F1F38DA5A9AFFE1664FB@musolino.id.au>
On 24/06/26 11:19, Alex Musolino wrote:
> Not really. It's not "a hack". It relies on the documented behaviour
> of grep(1) and /dev/null so I don't know why you are lacking
> confidence. I also don't know what you're getting at with xargs(1).
> Lastly, g(1) already does this exact thing for you; no need to pass an
> extra argument.
Never mind the reasoning about xargs(1), if no one is interested in the flag,
it means I'll continue adding /dev/null to my grep.
Thank you for the time spent.
next prev parent reply other threads:[~2024-06-26 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 2:24 shurizzle
2024-06-26 4:56 ` Alex Musolino
2024-06-26 11:18 ` me
2024-06-26 13:49 ` Alex Musolino
2024-06-26 14:08 ` me [this message]
2024-06-26 16:31 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-06-26 16:35 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-06-27 20:11 ` Romano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wjcgdmoxi535qmfv3mdmtrrlbfeutfj3o5gcf244jxgyqt6rv4@xhsiqs2il2zq \
--to=me@shurizzle.dev \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).