From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44409@debbugs.gnu.org
Subject: bug#44409: Example in manual no longer works
Date: Wed, 04 Nov 2020 07:32:42 +0800 [thread overview]
Message-ID: <87h7q6j9t1.5.fsf@jidanni.org> (raw)
In-Reply-To: <87mtzzj9fa.5.fsf@jidanni.org>
>>>>> "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?
If it were a binary file, the first grep,
>> $ grep --color -nH --null -e a /etc/motd
>> /etc/motd:2:The programs included with the Debian GNU/Linux system are free software;
>> /etc/motd:3:the exact distribution terms for each program are
>> described in the...
would fail.
But it doesn't. Only the second grep fails:
>> $ 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!!
Double proof:
$ file /etc/motd
/etc/motd: ASCII text
Thus we see that one cannot simply slap
"| grep bar | grep toto"
onto the end of a working grep command anymore!
Back when the manual was written, one could. But not anymore.
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.
(Or specific instructions need to be given: "Be sure to remove any
'--null' that emacs has stuck in, for this example to work.")
next prev parent reply other threads:[~2020-11-03 23:32 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 [this message]
2020-11-04 3:24 ` Eli Zaretskii
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=87h7q6j9t1.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=44409@debbugs.gnu.org \
--cc=eliz@gnu.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.