From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 44409-done@debbugs.gnu.org
Subject: bug#44409: Example in manual no longer works
Date: Wed, 04 Nov 2020 05:24:40 +0200 [thread overview]
Message-ID: <83v9elby87.fsf@gnu.org> (raw)
In-Reply-To: <87h7q6j9t1.5.fsf@jidanni.org> (message from 積丹尼 Dan Jacobson on Wed, 04 Nov 2020 07:32:42 +0800)
> From: 積丹尼 Dan Jacobson <jidanni@jidanni.org>
> Cc: bug-gnu-emacs@gnu.org, 44409@debbugs.gnu.org
> Date: Wed, 04 Nov 2020 07:32:42 +0800
>
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>
> EZ> The example in the manual doesn't mention /etc/motd of any other binary file. It uses text files, where this issue doesn't exist.
>
> Since when is /etc/motd a binary file?
I didn't say it was.
> >> $ grep --color -nH --null -e a /etc/motd | grep x
> >> Binary file (standard input) matches
>
> So we see the issue indeed exists with text files!!
No, it exists if you use Grep incorrectly.
> EZ> Yes, but you need to edit that prompt anyway in order to type the
> EZ> command with a pipe, so the original prompt doesn't matter much.
>
> No!
>
> In the past one could simply slap the pipe(s) on to the back.
>
> Now that no longer works.
>
> Therefore the example needs to be rewritten to make it work again.
The example already works without any changes, so it doesn't need to
be rewritten.
> (Or specific instructions need to be given: "Be sure to remove any
> '--null' that emacs has stuck in, for this example to work.")
That's the stuff for Grep manual, not for Emacs.
So I don't see any problem here to fix, and I'm closing this bug
report.
prev parent reply other threads:[~2020-11-04 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 5:28 bug#44409: Example in manual no longer works 積丹尼 Dan Jacobson
2020-11-03 7:16 ` Eli Zaretskii
2020-11-03 7:47 ` 積丹尼 Dan Jacobson
2020-11-03 11:16 ` Eli Zaretskii
2020-11-03 23:32 ` 積丹尼 Dan Jacobson
2020-11-04 3:24 ` Eli Zaretskii [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=83v9elby87.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44409-done@debbugs.gnu.org \
--cc=jidanni@jidanni.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.
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.