From: Joel Reicher <joel.reicher@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: outline-minor-mode heading levels in C, C++, and html
Date: Thu, 15 Aug 2024 22:34:41 +1000 [thread overview]
Message-ID: <86bk1um0bi.fsf@gmail.com> (raw)
In-Reply-To: <pfAKOBShDwpbb5pxv0RrcV6c57fE1XO-JBIdL8L5cKBaHO2-vJY5SZvqz3K6fJAuVHWZytwYacnAbs66fCNgS7JnUNPuIUqtxp9dw6WOtk0=@protonmail.com> (Heime's message of "Wed, 14 Aug 2024 13:58:24 +0000")
Heime <heimeborgia@protonmail.com> writes:
> In elisp one uses
>
> ;;; Level 1 Heading
> ;;;; Level 2 Heading
> ;;;;; Level 3 Heading
This is common, but not universal, and is not part of elisp.
For example advice.el in my Emacs installation has this:
;; @ Overview, or how to read this file:
;; ===================================== You can use
;; `outline-mode' to help you read this documentation (set
;; `outline-regexp' to `";; @+"').
You can see that very section of comments uses the alternative
convention that it describes, and that's the important point: it's
a *convention*.
One way you might be able to see the convention in use (if any) by
a particular mode, or file local or directory local variables, is
to check the value of outline-regexp from a buffer with the file
and mode you're interested in.
Regards,
- Joel
next prev parent reply other threads:[~2024-08-15 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 8:54 outline-minor-mode heading levels in C, C++, and html Heime
2024-08-14 11:53 ` Joel Reicher
2024-08-14 13:58 ` Heime
2024-08-14 16:45 ` Yuri Khan
2024-08-14 16:55 ` Heime
2024-08-14 18:08 ` Yuri Khan
2024-08-14 18:49 ` Heime
2024-08-15 12:34 ` Joel Reicher [this message]
2024-08-15 12:40 ` Joel Reicher
2024-08-15 13:40 ` Heime
2024-08-16 0:05 ` Joel Reicher
2024-08-16 0:23 ` Heime
2024-08-16 11:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-08-17 11:48 ` Joel Reicher
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=86bk1um0bi.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--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.
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.