From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>, Simon Lang <Simon.lang@outlook.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
"41766@debbugs.gnu.org" <41766@debbugs.gnu.org>
Subject: bug#41766: Make it possible to change regexp to identify and highlight grep matches via customization
Date: Thu, 11 Jun 2020 01:14:20 +0300 [thread overview]
Message-ID: <85a777f6-cf5e-9a05-7156-35a295713b89@yandex.ru> (raw)
In-Reply-To: <87bllqoag3.fsf@mail.linkov.net>
On 11.06.2020 00:52, Juri Linkov wrote:
> In the long run what should be customizable is not escape sequences,
> but a choice of the grep program with a list of such options:
>
> "GNU grep"
> "ripgrep"
> ...
That could simply be done by adding :tag to each option value, right?
next prev parent reply other threads:[~2020-06-10 22:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 20:25 bug#41766: Make it possible to change regexp to identify and highlight grep matches via customization Simon Lang
2020-06-08 23:18 ` Juri Linkov
2020-06-09 0:44 ` Dmitry Gutov
2020-06-09 7:58 ` Simon Lang
2020-06-09 11:55 ` Basil L. Contovounesios
2020-06-09 12:45 ` Simon Lang
2020-06-09 14:32 ` Basil L. Contovounesios
2020-06-09 14:43 ` Eli Zaretskii
2020-06-10 21:11 ` Simon Lang
2020-06-10 21:52 ` Juri Linkov
2020-06-10 22:14 ` Dmitry Gutov [this message]
2020-06-10 23:10 ` Juri Linkov
2020-06-10 23:24 ` Dmitry Gutov
2020-06-13 9:51 ` Simon Lang
2020-06-13 22:50 ` Juri Linkov
2020-06-13 6:50 ` Eli Zaretskii
2020-06-13 9:48 ` Simon Lang
2020-09-27 12:56 ` Lars Ingebrigtsen
2020-06-09 12:15 ` Dmitry Gutov
2020-06-09 12:41 ` Simon Lang
2020-06-09 14:24 ` Eli Zaretskii
[not found] <0e6ad4aefa2743f1b0d6ba4315a9e91b@VI1PR10MB2800.EURPRD10.PROD.OUTLOOK.COM>
2020-06-14 9:12 ` Simon Lang
2020-06-14 23:08 ` Juri Linkov
2020-06-22 19:09 ` Simon Lang
2020-06-22 23:50 ` Juri Linkov
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=85a777f6-cf5e-9a05-7156-35a295713b89@yandex.ru \
--to=dgutov@yandex.ru \
--cc=41766@debbugs.gnu.org \
--cc=Simon.lang@outlook.com \
--cc=contovob@tcd.ie \
--cc=juri@linkov.net \
/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).