From: "Augustin Chéneau via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>, Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 66152@debbugs.gnu.org
Subject: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sun, 14 Jan 2024 11:21:48 +0100 [thread overview]
Message-ID: <c9b8d71d-d769-44f5-9357-cdc8306208d6@mailo.com> (raw)
In-Reply-To: <CADwFkmmsfix1dxrMrqCB7XtRCnGvwtKvWChbMSgk3kFNHuAfjA@mail.gmail.com>
Le 14/01/2024 à 06:33, Stefan Kangas a écrit :
> Yuan Fu <casouri@gmail.com> writes:
>
>> I had a look again, the first patch is applied, the second patch is fixed in
>> another report,
>
> Thanks.
>
>> the third patch is still in discussion. Augustin said he’ll
>> clean it up and extend it to apply to other modes if it’s desirable. I think
>> it’s good to have, we just need to make sure it doesn’t bring any
>> regression. Also I don’t know how widely used is this kind of comments and how
>> important it is.
>
> I guess it's for indenting this kind of comment?
>
> /*---------.
> | %param. |
> `---------*/
>
> I have no idea either. Are there any significant projects that use it?
Yes, it is for indenting these kind of comments.
It depends on your definition of "significant", but GNU Bison sometimes
uses it (example:
<https://git.savannah.gnu.org/cgit/bison.git/tree/src/getargs.c#n171>).
However I don't know if it is more widely used, if some convention exist
or if pretty much everyone has his own style.
It could be more annoying than helpful if it messes with your personal
style, though.
In any case I won't be able to contribute for a while, as I recently
moved to a new company. They never did copyright assignment and they are
quite fussy (understandably) on copyright issues.
next prev parent reply other threads:[~2024-01-14 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 11:23 bug#66152: 30.0.50; Missing indent rules in c-ts-mode Augustin Chéneau
2023-09-26 12:29 ` Augustin Chéneau
2023-09-29 7:17 ` Eli Zaretskii
2023-10-05 7:16 ` Eli Zaretskii
2023-12-11 2:16 ` Yuan Fu
2024-01-10 21:31 ` Stefan Kangas
2024-01-11 6:24 ` Eli Zaretskii
2024-01-13 7:07 ` Yuan Fu
2024-01-14 5:33 ` Stefan Kangas
2024-01-14 7:09 ` Eli Zaretskii
2024-01-14 10:21 ` Augustin Chéneau via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-11 2:41 ` Yuan Fu
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=c9b8d71d-d769-44f5-9357-cdc8306208d6@mailo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=66152@debbugs.gnu.org \
--cc=btuin@mailo.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).