From: Juri Linkov <juri@jurta.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13892@debbugs.gnu.org
Subject: bug#13892: 24.3.50; Provide for customizing default regexp in hi-lock commands
Date: Thu, 07 Mar 2013 11:09:29 +0200 [thread overview]
Message-ID: <87ehfrmv92.fsf@mail.jurta.org> (raw)
In-Reply-To: <87fw08za2u.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 06 Mar 2013 23:26:09 +0530")
> +(defvar hi-lock-read-regexp-defaults-function
> + 'hi-lock-read-regexp-defaults
> + "Function that provides default regexp(s) for highlighting commands.
> +This function should take one argument OP and return one of nil,
> +a regexp or a list of regexps for use with highlighting command
> +OP. OP, a symbol, can be one of `phrase', `line' or `nil'
> +signifying commands `hi-lock-face-phrase-buffer',
> +`hi-lock-line-face-buffer' and `hi-lock-face-buffer'
> +respectively.
Requiring an additional argument `op' means that we wouldn't
be able to customize `hi-lock-read-regexp-defaults-function'
to just `find-tag-default' or `find-tag-default-as-regexp'.
I think there is no need to distinguish between different
hi-lock commands since one user would very likely prefer
the one way to get the default for all hi-lock commands,
so you could call `hi-lock-read-regexp-defaults-function'
without arguments.
next prev parent reply other threads:[~2013-03-07 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 17:56 bug#13892: 24.3.50; Provide for customizing default regexp in hi-lock commands Jambunathan K
2013-03-07 9:09 ` Juri Linkov [this message]
2013-03-07 10:31 ` Jambunathan K
2013-03-08 4:29 ` Jambunathan K
2013-03-10 18:31 ` 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=87ehfrmv92.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13892@debbugs.gnu.org \
--cc=kjambunathan@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 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).