From: Jean Louis <bugs@gnu.support>
To: William Xu <william.xwl@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to highlight UUID in all buffes?
Date: Sat, 15 Oct 2022 13:42:30 +0300 [thread overview]
Message-ID: <Y0qOlifqtHc09IQw@protected.localdomain> (raw)
In-Reply-To: <s3go7udqste.fsf@gmail.com>
* William Xu <william.xwl@gmail.com> [2022-10-15 13:36]:
> Jean Louis <bugs@gnu.support> writes:
>
> > I have tried this:
> >
> > (font-lock-add-keywords 'mail-mode '((thing-at-point-uuid-regexp 1 'link)))
>
> Try:
>
> (font-lock-add-keywords 'mail-mode `((,(concat "\\(" thing-at-point-uuid-regexp "\\)") 1 'link)))
64ec985c-5aeb-4e24-952f-ef66b7f8bf1e
When I do:
{M-x font-lock-update RET}
I get:
Debugger entered--Lisp error: (void-function thing-at-point-uuid-regexp)
thing-at-point-uuid-regexp(565)
font-lock-fontify-keywords-region(1 565 nil)
font-lock-default-fontify-region(1 565 nil)
font-lock-fontify-region(1 565)
font-lock-update(nil)
funcall-interactively(font-lock-update nil)
call-interactively(font-lock-update record nil)
command-execute(font-lock-update record)
execute-extended-command(nil "font-lock-update" "font-lock-update")
funcall-interactively(execute-extended-command nil "font-lock-update" "font-lock-update")
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-10-15 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 7:11 How to highlight UUID in all buffes? Jean Louis
2022-10-15 7:17 ` Emanuel Berg
2022-10-15 7:41 ` Jean Louis
2022-10-15 8:11 ` William Xu
2022-10-15 9:33 ` Jean Louis
2022-10-15 10:34 ` William Xu
2022-10-15 10:42 ` Jean Louis [this message]
2022-10-15 11:03 ` William Xu
2022-10-15 10:55 ` Daniel Martín
2022-10-16 9:55 ` Jean Louis
2022-10-16 16:12 ` Bruno Barbier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y0qOlifqtHc09IQw@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=william.xwl@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.