From: Juri Linkov <juri@linkov.net>
To: Simon Lang <Simon.lang@outlook.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
"41766@debbugs.gnu.org" <41766@debbugs.gnu.org>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#41766: Make it possible to change regexp to identify and highlight grep matches via customization
Date: Sun, 14 Jun 2020 01:50:49 +0300 [thread overview]
Message-ID: <878sgqy3zq.fsf@mail.linkov.net> (raw)
In-Reply-To: <VI1PR10MB28003D0A94A7AAFB04D5867C809E0@VI1PR10MB2800.EURPRD10.PROD.OUTLOOK.COM> (Simon Lang's message of "Sat, 13 Jun 2020 09:51:29 +0000")
> Maybe also a way to easily register new search tools? Otherwise one might
> be locked into the available options again - and if there is a new tool the
> interface might be not that stable, so there is the danger that it breaks
> until there is a new emacs release.
No problem, you can even dynamically add an option available only
when a grep program is installed:
(defcustom grep-program nil
"The default grep program for `grep-command' and `grep-find-command'.
This variable's value takes effect when `grep-compute-defaults' is called."
:type `(choice (const :tag "GNU grep" (purecopy "grep"))
,@(if (executable-find "rg") '((const :tag "ripgrep" "rg")))
(string :tag "Other grep program")
(const :tag "Not Set" nil))
:version "28.1")
Or for a completely new tool:
(nconc (get 'grep-program 'custom-type) '((const :tag "ripgrep" "rg")))
next prev parent reply other threads:[~2020-06-13 22:50 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
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 [this message]
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=878sgqy3zq.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=41766@debbugs.gnu.org \
--cc=Simon.lang@outlook.com \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
/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).