From: Heime <heimeborgia@protonmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Special hilighting for comments
Date: Sun, 11 Dec 2022 05:06:15 +0000 [thread overview]
Message-ID: <4ZoH0AfcsVq81IEDuPRDmyY7DLjaiJmzCbYt-YxyJ7xctHSDgFyVUYjvcKkdcLu7R8T3fpGVHRyHF0D-aqMnwB9of-JUtbkF7tml7hbirDo=@protonmail.com> (raw)
In-Reply-To: <Y5VbMdCWjsT/52uP@protected.localdomain>
------- Original Message -------
On Sunday, December 11th, 2022 at 4:23 AM, Jean Louis <bugs@gnu.support> wrote:
> * Heime heimeborgia@protonmail.com [2022-12-11 05:38]:
>
> > Would you know the problem with the following regexp
>
>
> ;; [something] other things
>
> (highlight-regexp "^;; \\[.*$")
>
> The above works well. --> Jean
I would like to use a sub-expresion to highlight "[something]" only
next prev parent reply other threads:[~2022-12-11 5:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 2:42 Special hilighting for comments Heime
2022-12-10 6:12 ` Marcin Borkowski
2022-12-10 6:23 ` Heime
2022-12-10 8:13 ` Eli Zaretskii
2022-12-10 8:14 ` Eli Zaretskii
2022-12-10 8:30 ` Heime
2022-12-10 8:49 ` Eli Zaretskii
2022-12-10 10:53 ` Heime
2022-12-10 11:15 ` Eli Zaretskii
2022-12-10 11:26 ` Heime
2022-12-10 14:21 ` Eli Zaretskii
2022-12-10 14:28 ` Heime
2022-12-10 15:52 ` Jean Louis
2022-12-10 17:11 ` Heime
2022-12-10 17:16 ` Eli Zaretskii
2022-12-10 17:39 ` Heime
2022-12-10 17:57 ` Thibaut Verron
2022-12-10 18:32 ` Eli Zaretskii
2022-12-12 0:59 ` Heime
2022-12-10 19:44 ` Jean Louis
2022-12-11 2:10 ` Heime
2022-12-11 2:37 ` Heime
2022-12-11 4:23 ` Jean Louis
2022-12-11 5:06 ` Heime [this message]
2022-12-11 9:06 ` Jean Louis
2022-12-11 6:54 ` tomas
2022-12-11 6:59 ` Heime
2022-12-11 7:24 ` tomas
2022-12-11 7:33 ` Heime
2022-12-11 7:47 ` tomas
2022-12-11 7:52 ` Heime
2022-12-11 8:55 ` tomas
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='4ZoH0AfcsVq81IEDuPRDmyY7DLjaiJmzCbYt-YxyJ7xctHSDgFyVUYjvcKkdcLu7R8T3fpGVHRyHF0D-aqMnwB9of-JUtbkF7tml7hbirDo=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.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 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.