all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: bug#6843 <6843@debbugs.gnu.org>, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#6843: grep-mode and filenames with colons
Date: Sun, 30 Jul 2017 11:01:36 -0400	[thread overview]
Message-ID: <87d18i7yun.fsf@users.sourceforge.net> (raw)
In-Reply-To: <b3ab58d3-c4eb-6243-ddad-a3b201a86b08@yandex.ru> (Dmitry Gutov's message of "Thu, 27 Jul 2017 15:10:40 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> I'd prefer to have either grep-with-null-regexp-alist and
> grep-[without-null-]-regexp-alist, or grep-regexp-alist and
> grep-fallback-regexp-alist. Just a suggestion.
>

[...]

>>
>>> If the numbers are the same, we could keep the variable's name the same as
>>> well. As a result, most third-party code would continue to simply work.
>>
>> Might be worth using explicitly numbered groups to keep the numbers for
>> FILE and COLUMN the same though.
>
> Yes, I think it will be a good idea. Provided we can combine it with
> renaming either of the variables back to grep-regexp-alist. Otherwise,
> any backward compatibility is broken anyway.

That part is already covered by this, no?

    (defvaralias 'grep-regex-alist 'grep-with-null-regexp-alist)
    (make-obsolete-variable
     'grep-regex-alist "Call `grep-regexp-alist' instead." "26.1")







  parent reply	other threads:[~2017-07-30 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 11:20 bug#6843: 23.1; grep-mode and filenames with colors Ethan Glasser-Camp
2017-07-26 23:32 ` bug#6843: grep-mode and filenames with colons npostavs
2017-07-27 12:10   ` Dmitry Gutov
2017-07-27 17:20     ` Eli Zaretskii
2017-07-30 15:01     ` npostavs [this message]
2017-08-01 13:28       ` Dmitry Gutov

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=87d18i7yun.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=6843@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=schwab@linux-m68k.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.