From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32093@debbugs.gnu.org, dak@gnu.org, michael.albinus@gmx.de
Subject: bug#32093: 27.0.50; M-x grep appends /dev/null to command line
Date: Tue, 10 Jul 2018 18:55:25 +0300 [thread overview]
Message-ID: <834lh7gk5u.fsf@gnu.org> (raw)
In-Reply-To: <87pnzwccfh.fsf@gmail.com> (message from Noam Postavsky on Mon, 09 Jul 2018 17:43:46 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 32093@debbugs.gnu.org, dak@gnu.org, michael.albinus@gmx.de
> Date: Mon, 09 Jul 2018 17:43:46 -0400
>
> > But is there a good reason why we use HELLO for that? Why not README,
> > say, whose first line will always start with "Copyright"?
>
> I don't think there's a reason to use HELLO in particular. etc/README
> doesn't have Copyright on the first line, but it does have COPYRIGHT at
> the beginning of a line (I think we do want something specifically in
> etc/, because we know `data-directory' tells us where to find it).
I meant the top-level README, which I think always will include a
Copyright line.
But that was just a suggestion. I see Paul decided to continue using
etc/HELLO, just with a different search patterns. If we are OK with
that, we can put that issue to rest.
There's still a broader issue of whether a test done with plain 'grep'
holds for any other "grep-like" program. I'm not sure what to do with
that.
We could even take one more step back and ask ourselves why do we need
this particular test. I believe it's because we want to support file
names with embedded newlines, in which case perhaps such niche use
cases could be supported by a special command or a special user
option? I mean, it sounds strange to let a tail wag the dog, no?
next prev parent reply other threads:[~2018-07-10 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 9:33 bug#32093: 27.0.50; M-x grep appends /dev/null to command line David Kastrup
2018-07-08 9:51 ` Michael Albinus
2018-07-08 9:53 ` David Kastrup
2018-07-08 10:05 ` Michael Albinus
2018-07-08 11:17 ` David Kastrup
2018-07-08 12:19 ` Noam Postavsky
2018-07-08 12:30 ` David Kastrup
2018-07-08 19:04 ` Eli Zaretskii
2018-07-08 19:11 ` David Kastrup
2018-07-09 21:43 ` Noam Postavsky
2018-07-10 7:33 ` David Kastrup
2018-07-10 15:55 ` Eli Zaretskii [this message]
2018-07-10 22:04 ` Noam Postavsky
2018-07-09 23:10 ` Noam Postavsky
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=834lh7gk5u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32093@debbugs.gnu.org \
--cc=dak@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=npostavs@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.