From: Heime <heimeborgia@protonmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Introducing face in comments for various modes
Date: Mon, 12 Dec 2022 02:24:08 +0000 [thread overview]
Message-ID: <flxVOTDfrBOyZEXThpBWo-TVXzBr0SCIhGmic0CCOGgRsjJybtuYyoXc711nFrtV8t_AahM6b9tUWnfvc15f_Btl8vmq35pGa57yt_S3HIk=@protonmail.com> (raw)
In-Reply-To: <jwv7cyxlu4v.fsf-monnier+emacs@gnu.org>
------- Original Message -------
On Sunday, December 11th, 2022 at 5:40 PM, Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> BTW, there is a related convention in ELisp code where comments that
> start in column 0 and which are introduced with 3 or more semi-colons
> are considered sectioning headers (where ";;;" means a top-level
> header, ";;;;" a subheader, ";;;;;" a subsubheader, ...).
>
> I'd be happy if Emacs were changed to highlighting those.
>
> Stefan
Yes. I use headings as you describe to identify sections of code that focus on a particular task. But I also wanted to have some lower level categorisation (within a function, say) to group some descriptions together.
> Heime [2022-12-11 15:35:41] wrote:
>
> > The following uses `hi-lock` to change the foreground of comments matching
> > a regexp. This is implemented for emacs-lisp files where comments start
> > with ";;".
> >
> > I would like to extend this for other programming languages besides emacs-lisp
> > files, using the relevant comment character automatically for that language.
> >
> > (defface elfa-face
> > '((t :foreground "magenta"))
> > "Face for comment headings.")
> >
> > (defun elfa-regexp (&optional actm)
> > "Identify comment category ';; [Category]'."
> > (highlight-regexp
> > "^;;\s+\\[.+\\].*$" 'elfa-face))
> >
> > (defun elfa-category ()
> > "TODO."
> > (interactive)
> > (add-to-list 'auto-mode-alist '("\\.el\\'" . hi-lock-mode))
> > (add-hook 'emacs-lisp-mode-hook 'hi-lock-mode t)
> > (add-hook 'hi-lock-mode-hook 'elfa-regexp))
>
>
next prev parent reply other threads:[~2022-12-12 2:24 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 [this message]
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
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='flxVOTDfrBOyZEXThpBWo-TVXzBr0SCIhGmic0CCOGgRsjJybtuYyoXc711nFrtV8t_AahM6b9tUWnfvc15f_Btl8vmq35pGa57yt_S3HIk=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).