From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: Heime <heimeborgia@protonmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Introducing face in comments for various modes
Date: Tue, 13 Dec 2022 09:17:02 +0100 [thread overview]
Message-ID: <trinity-81cf9790-994e-4bda-9bae-951507113e49-1670919422544@3c-app-mailcom-bs16> (raw)
In-Reply-To: <Y5gvP6wx13/2SMLs@protected.localdomain>
> Sent: Tuesday, December 13, 2022 at 7:52 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: "Heime" <heimeborgia@protonmail.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Introducing face in comments for various modes
>
>
> Heime, I like the idea of highlighting comments, though I do it this
> way to specify (syntax comment-start) as that works for multiple
> modes.
>
> ; one
> ;; two
> ;;; three
> ;;;; and more
>
> ;;; Highlighting comments
>
> (setq rcd-regexp-comment (rx line-start
> (one-or-more (syntax comment-start))
> (one-or-more space)
> (group (one-or-more not-newline))
> line-end))
>
> ;; (highlight-regexp regexp nil 1)
> ;; (unhighlight-regexp regexp)
>
> --
> Jean
Would your procedure not conflict when people use outline-mode. Such comments
will end up getting folded by tho outline commands, something the OP does not want.
next prev parent reply other threads:[~2022-12-13 8:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 15:35 Introducing face in comments for various modes Heime
2022-12-11 17:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-12 2:24 ` Heime
2022-12-12 3:00 ` Heime
2022-12-12 8:49 ` Thibaut Verron
2022-12-12 9:21 ` Heime via Users list for the GNU Emacs text editor
2022-12-12 9:58 ` Thibaut Verron
2022-12-12 10:20 ` Heime
2022-12-12 10:50 ` Thibaut Verron
2022-12-12 11:55 ` Heime
2022-12-12 12:17 ` Thibaut Verron
2022-12-12 14:46 ` Heime
2022-12-12 15:22 ` Yuri Khan
2022-12-12 15:38 ` Thibaut Verron
2022-12-12 15:55 ` Christopher Dimech
2022-12-12 16:07 ` Christopher Dimech
2022-12-12 17:44 ` Stefan Monnier
2022-12-13 5:20 ` Christopher Dimech
2022-12-12 15:22 ` Stefan Monnier
2022-12-13 7:52 ` Jean Louis
2022-12-13 8:04 ` Heime
2022-12-13 8:30 ` Heime
2022-12-13 9:35 ` Thibaut Verron
2022-12-13 9:46 ` Heime
2022-12-13 10:05 ` Thibaut Verron
2022-12-13 10:24 ` Christopher Dimech
2022-12-13 10:40 ` Heime
2022-12-13 10:45 ` Thibaut Verron
2022-12-13 10:49 ` Heime
2022-12-13 15:00 ` Heime
2022-12-13 12:37 ` Jean Louis
2022-12-13 14:00 ` Heime
2022-12-13 12:36 ` Jean Louis
2022-12-13 13:46 ` Heime
2022-12-13 12:35 ` Jean Louis
2022-12-13 8:17 ` Christopher Dimech [this message]
2022-12-13 19:19 ` Jean Louis
2022-12-12 15:20 ` Stefan Monnier
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=trinity-81cf9790-994e-4bda-9bae-951507113e49-1670919422544@3c-app-mailcom-bs16 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=heimeborgia@protonmail.com \
--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.
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).