unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: Stefan Monnier via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: outline-minor-mode heading levels in C, C++, and html
Date: Sat, 17 Aug 2024 21:48:30 +1000	[thread overview]
Message-ID: <86wmkf1ib5.fsf@gmail.com> (raw)
In-Reply-To: <jwvikw0k94h.fsf-monnier+emacs@gnu.org> (Stefan Monnier via Users list for the's message of "Fri, 16 Aug 2024 07:20:38 -0400")

Stefan Monnier via Users list for the GNU Emacs text editor 
<help-gnu-emacs@gnu.org> writes:

>> This is common, but not universal, and is not part of elisp.
>
> That depends whether you consider
>
>     @section Tips on Writing Comments
>
> to be part of the "definition" of ELisp.

It would depend on what you take to be a language's definition, of 
course, but I don't want to be philosophical.

I think many people take a language to be defined by the behaviour 
of the tooling for that language, although this understanding 
would probably vary according to experience, mindset, and 
hairstyle.

For a programming language the syntax would be determined by the 
compiler/interpreter, and the semantics by the runtime behaviour.

That's why I think it's useful to regard this commenting 
idiom/convention as not part of elisp, because, as far as I know, 
it's not "comprehended" by the runtime tooling.

It is, however, comprehended by the outline-regexp value set in 
lisp-mode, so I think it might make sense to talk about this as 
lisp-mode's comment syntax, because although a major mode is 
usually regarded as supporting a language rather than defining 
one, the major mode in this case is the tooling that determines 
the behaviour.

Cheers,

        - Joel



      reply	other threads:[~2024-08-17 11:48 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
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 [this message]

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=86wmkf1ib5.fsf@gmail.com \
    --to=joel.reicher@gmail.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).