From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org, me@shurizzle.dev
Subject: Re: [9front] [PATCH] feat(grep): add -H flag
Date: Wed, 26 Jun 2024 09:31:13 -0700 [thread overview]
Message-ID: <8ceffac2e94d3708@orthanc.ca> (raw)
In-Reply-To: <t56mgjsckrql3abweyxecqphxkse2yoeg22uwiiliv5gulrqge@oehbxqrnatrw>
me@shurizzle.dev writes:
> That's exactly what I do now, but a flag gives me more confidence
> than a hack.
It's not a 'hack'. This is idiomatic usage going back to when
grep grew a -l flag.
next prev parent reply other threads:[~2024-06-26 16:33 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
2024-06-26 16:31 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
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=8ceffac2e94d3708@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.org \
--cc=me@shurizzle.dev \
/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).