From: Michael Albinus <michael.albinus@gmx.de>
To: David Kastrup <dak@gnu.org>
Cc: 32093@debbugs.gnu.org
Subject: bug#32093: 27.0.50; M-x grep appends /dev/null to command line
Date: Sun, 08 Jul 2018 11:51:23 +0200 [thread overview]
Message-ID: <87pnzyawdg.fsf@gmx.de> (raw)
In-Reply-To: <87lgamdqcb.fsf@fencepost.gnu.org> (David Kastrup's message of "Sun, 08 Jul 2018 11:33:24 +0200")
David Kastrup <dak@gnu.org> writes:
> I did not ask for /dev/null to be appended to the command line, and
> previous incantations didn't do it. Obviously, not all grep-kind
> programs are happy about that change.
--8<---------------cut here---------------start------------->8---
grep-use-null-device is a variable defined in ‘grep.el’.
Its value is ‘auto-detect’
Documentation:
If t, append the value of ‘null-device’ to ‘grep’ commands.
This is done to ensure that the output of grep includes the filename of
any match in the case where only a single file is searched, and is not
necessary if the grep program used supports the ‘-H’ option.
In interactive usage, the actual value of this variable is set up
by ‘grep-compute-defaults’; to change the default value, use
Customize or call the function ‘grep-apply-setting’.
You can customize this variable.
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
next prev parent reply other threads:[~2018-07-08 9:51 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnzyawdg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=32093@debbugs.gnu.org \
--cc=dak@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).