From: "有澤 健治" <karisawa@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] grep: always show path with '-n'
Date: Sat, 5 Feb 2022 13:58:36 +0900 [thread overview]
Message-ID: <b8954d1f-bb63-9b10-7037-a56dd0c8647e@gmail.com> (raw)
In-Reply-To: <EC7AE28A319953480E1CA64DF9DC4BE3@eigenstate.org>
Hello,
On 2022/02/03 8:01, ori@eigenstate.org wrote:
> And it still does something sensible for stdin:
>
> % grep -n asdf
> asdf
> stdin:1: asdf
>
> Does this make sense to people?
Isn't it logically better:
% grep -n asdf
asdf
:1: asdf
prev parent reply other threads:[~2022-02-05 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 23:01 ori
2022-02-03 5:14 ` unobe
2022-02-03 7:04 ` Steve Simon
2022-02-03 16:47 ` ori
2022-02-03 19:04 ` Nicola Girardi
2022-02-04 0:47 ` ori
2022-02-04 0:48 ` ori
2022-02-04 22:00 ` Nicola Girardi
2022-02-05 16:57 ` hiro
2022-02-05 17:06 ` Stanley Lieber
2022-02-05 18:00 ` hiro
2022-02-04 12:39 ` Alex Musolino
2022-02-05 4:58 ` 有澤 健治 [this message]
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=b8954d1f-bb63-9b10-7037-a56dd0c8647e@gmail.com \
--to=karisawa@gmail.com \
--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).