From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eric Hanchrow <eric.hanchrow@gmail.com>
Cc: 27873@debbugs.gnu.org
Subject: bug#27873: 26.0.50; M-x grep broken
Date: Sun, 30 Jul 2017 16:34:23 -0400 [thread overview]
Message-ID: <CAM-tV-8uLqWa1gD1bcM0LWDhesyuJfzpBRzFR9fhyLMPOjBAgw@mail.gmail.com> (raw)
In-Reply-To: <CAHZoxq9XD5YNSz4FDX_wtWwXzpe2+zftGCk0NzXm24WBbSGGJQ@mail.gmail.com>
On Sun, Jul 30, 2017 at 4:25 PM, Eric Hanchrow <eric.hanchrow@gmail.com> wrote:
> I suspect you've subtly changed the semantics of the grep command, by
> assuming that the hits are teminated by a 0 byte. This is a good thing, but
> it seems to have broken a command I've written myself -- that is, when I run
>
> cd /Users/erichanchrow/git-repositories/3rd-party/emacs/ && git grep
> --perl-regexp -I -n --ignore-case -e hanchrow
>
> I see ... well, it's hard to describe, but the hits aren't highlighted in
> the color I expect, and C-x ` just says "Moved past last grep hit". But,
> not surprisingly, if I add --null to that command line, it works nicely.
>
> So now I will need to adjust my command based on which version of grep.el
> I've got. Is there some programmatic way that I can tell which version I've
> got? I.e., perhaps I can write something like "if boundp
> 'grep-with-null-regexp-alist then add --null to my command, else leave it
> out"?
It should work to just customize `grep-use-null-filename-separator' to
nil. Then you should have the old behaviour again.
I'm currently leaning towards making it default to nil actually, to
avoid the hassle in cases like the one you've described above (see
also Bug#27840).
prev parent reply other threads:[~2017-07-30 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 0:02 bug#27873: 26.0.50; M-x grep broken Eric Hanchrow
2017-07-30 0:08 ` bug#27873: Probably a dupe of #27840 Eric Hanchrow
2017-07-30 15:32 ` bug#27873: 26.0.50; M-x grep broken npostavs
2017-07-30 18:48 ` Eric Hanchrow
2017-07-30 20:08 ` npostavs
[not found] ` <CAHZoxq9XD5YNSz4FDX_wtWwXzpe2+zftGCk0NzXm24WBbSGGJQ@mail.gmail.com>
2017-07-30 20:34 ` Noam Postavsky [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=CAM-tV-8uLqWa1gD1bcM0LWDhesyuJfzpBRzFR9fhyLMPOjBAgw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=27873@debbugs.gnu.org \
--cc=eric.hanchrow@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.