unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 14427@debbugs.gnu.org
Subject: bug#14427: 24.3.50; Highlight symbol at point
Date: Sun, 02 Jun 2013 15:31:48 +0530	[thread overview]
Message-ID: <87vc5wvnjn.fsf@gmail.com> (raw)
In-Reply-To: <87ppwlb6tx.fsf@mail.jurta.org> (Juri Linkov's message of "Tue, 21 May 2013 01:54:34 +0300")


If you could commit this change, I can start using it right away.  I
have no firm opinion on whether `hi-lock-auto-select-face' should come
from user setting or be let bound.

Remember to provide a keybinding in hi-lock mode.  I suggest C-x w
"dot".

Juri Linkov <juri@jurta.org> writes:

> This feature request mostly doesn't depend on the outcome of bug#14405.
> I don't know why Jambunathan didn't propose this feature earlier, but it
> logically follows from his other improvements in hi-lock.el, i.e. the
> feature that doesn't ask for a face and automatically uses the next face
> from the list of available faces suggests also a command that doesn't ask
> for a symbol and automatically uses the symbol at point:
>
> === modified file 'lisp/hi-lock.el'
> --- lisp/hi-lock.el	2013-03-31 13:34:35 +0000
> +++ lisp/hi-lock.el	2013-05-20 22:52:54 +0000
> @@ -483,6 +461,27 @@ (defun hi-lock-face-phrase-buffer (regex
>    (unless hi-lock-mode (hi-lock-mode 1))
>    (hi-lock-set-pattern regexp face))
>  
> +;;;###autoload
> +(defalias 'highlight-symbol-at-point 'hi-lock-face-symbol-at-point)
> +;;;###autoload
> +(defun hi-lock-face-symbol-at-point ()
> +  "Set face of each match of the symbol at point.
> +Use `find-tag-default-as-symbol-regexp' to retrieve the symbol at point.
> +Use non-nil `hi-lock-auto-select-face' to retrieve the next face
> +from `hi-lock-face-defaults' automatically.
> +
> +Use Font lock mode, if enabled, to highlight symbol at point.
> +Otherwise, use overlays for highlighting.  If overlays are used,
> +the highlighting will not update as you type."
> +  (interactive)
> +  (let* ((regexp (hi-lock-regexp-okay
> +		  (find-tag-default-as-symbol-regexp)))
> +	 (hi-lock-auto-select-face t)
> +	 (face (hi-lock-read-face-name)))
> +    (or (facep face) (setq face 'hi-yellow))
> +    (unless hi-lock-mode (hi-lock-mode 1))
> +    (hi-lock-set-pattern regexp face)))
> +
>  (defun hi-lock-keyword->face (keyword)
>    (cadr (cadr (cadr keyword))))    ; Keyword looks like (REGEXP (0 'FACE) ...).
>  





  parent reply	other threads:[~2013-06-02 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 22:54 bug#14427: 24.3.50; Highlight symbol at point Juri Linkov
2013-05-20 23:28 ` Juri Linkov
2013-05-21 19:07   ` Juri Linkov
2013-06-02 10:01 ` Jambunathan K [this message]
2013-06-02 10:04   ` Jambunathan K
2013-06-03  8:54     ` 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=87vc5wvnjn.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=14427@debbugs.gnu.org \
    --cc=juri@jurta.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 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).