unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 14438-done@debbugs.gnu.org
Subject: bug#14438: 24.3.50; Honor `hi-lock-auto-select-face' for non-interactive use
Date: Mon, 03 Jun 2013 11:59:10 +0300	[thread overview]
Message-ID: <87k3mba7sy.fsf@mail.jurta.org> (raw)
In-Reply-To: <878v36ka1g.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 22 May 2013 23:57:10 +0300")

>>       (add-hook 'occur-mode-find-occurrence-hook
>>                 (lambda nil (highlight-regexp
>>                              (find-tag-default-as-regexp))))
>
> You could use
>
>       (add-hook 'occur-mode-find-occurrence-hook
>                 (lambda nil (highlight-regexp
>                              (find-tag-default-as-regexp)
> 			     (let ((hi-lock-auto-select-face t))
> 			       (hi-lock-read-face-name)))))
>
> like I proposed to do in bug#14427 to get the next face automatically.
>
> BTW, what do you think about bug#14405 that adds a new defcustom
> `read-regexp-defaults-function' that is more user-friendly
> to customize than changing the values of several functions like
> `occur-read-regexp-defaults-function' and
> `hi-lock-read-regexp-defaults-function'?

It seems this report can be closed since `hi-lock-auto-select-face'
works as expected for interactive commands, and `hi-lock-read-face-name'
can be added as the second arg of the `highlight-regexp' call
when used programmatically:

      (add-hook 'occur-mode-find-occurrence-hook
                (lambda nil (highlight-regexp
                              (find-tag-default-as-regexp)
                              (hi-lock-read-face-name))))





      reply	other threads:[~2013-06-03  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  8:02 bug#14438: 24.3.50; Honor `hi-lock-auto-select-face' for non-interactive use Jambunathan K
2013-05-22 20:57 ` Juri Linkov
2013-06-03  8:59   ` Juri Linkov [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

  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=87k3mba7sy.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=14438-done@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).