GNU bug report logs - #66152
Support indenting box comments in c-ts-mode

Previous Next

To reply to this bug, email your comments to 66152 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.0.50; Missing indent rules in c-ts-mode
Date: Fri, 22 Sep 2023 13:23:56 +0200

[Message part 1 (text/plain, inline)]

There are missing indent rules in c-ts-mode.
Currently there is no rule if an identifier in a declaration is on a new
line. In these two cases, "variable_name" is not indented:

static myttype *
variable_name;

static myttype
variable_name;

The new behavior is the same as c-mode.


In GNU Emacs 30.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version
 3.24.38, cairo version 1.17.8) of 2023-09-19 built on inspiron-5567
Repository revision: 991bf3f0f5dff66794785ebfcc867611fe75e0da
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12302001
System Description: Arch Linux

Configured using:
 'configure PKG_CONFIG_PATH=/home/arch-aug/.opam/default/lib/pkgconfig:'

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBSYSTEMD LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG RSVG
SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER WEBP
X11 XDBE XIM XINPUT2 XPM GTK3 ZLIB

Important settings:
  value of $LANG: fr_FR.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  minibuffer-regexp-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message mailcap yank-media puny dired
dired-loaddefs rfc822 mml mml-sec password-cache epa derived epg rfc6068
epg-config gnus-util text-property-search mm-decode mm-bodies mm-encode
mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047
rfc2045 ietf-drums mm-util mail-prsvr mail-utils time-date subr-x
cl-loaddefs cl-lib rmc iso-transl tooltip cconv eldoc paren electric
uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel
term/x-win x-win term/common-win x-dnd touch-screen tool-bar dnd fontset
image regexp-opt fringe tabulated-list replace newcomment text-mode
lisp-mode prog-mode register page tab-bar menu-bar rfn-eshadow isearch
easymenu timer select scroll-bar mouse jit-lock font-lock syntax
font-core term/tty-colors frame minibuffer nadvice seq simple cl-generic
indonesian philippine cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek
romanian slovak czech european ethiopic indian cyrillic chinese
composite emoji-zwj charscript charprop case-table epa-hook
jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button loaddefs
theme-loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget keymap
hashtable-print-readable backquote threads dbusbind inotify lcms2
dynamic-setting system-font-setting font-render-setting cairo gtk
x-toolkit xinput2 x multi-tty move-toolbar make-network-process emacs)

Memory information:
((conses 16 37844 9140) (symbols 48 5209 0) (strings 32 13243 1761)
 (string-bytes 1 376699) (vectors 16 10300)
 (vector-slots 8 156214 14950) (floats 8 22 23) (intervals 56 220 0)
 (buffers 992 10))

[0001-Add-missing-indent-rules-in-c-ts-mode.patch (text/x-patch, attachment)]

Message #8 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
To: 66152 <at> debbugs.gnu.org
Subject: 30.0.50; Missing indent rules in c-ts-mode
Date: Tue, 26 Sep 2023 14:29:07 +0200

[Message part 1 (text/plain, inline)]

I found some more issues.

First, there is no rule for an element in an else clause:


if (true)
  do_something();
else
do_something_else();


"do_something_else" is not indented.

There is also something weird with the bsd indent style.  It indents 
do_something and do_something_else to parent-bol with 0 offset, so the 
result is:

if (true)
do_something();
else
do_something_else();


It is very different from the bsd style from c-mode, which produces this:

if (true)
	do_something();
else
	do_something_else();

By looking at random files from OpenBSD, they do indent their 
expressions inside if and else:

<https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/net/bsd-comp.c?rev=1.17&content-type=text/plain>
(lines 277, 484, and 527)



Also there is a second patch which tries to handle specific types of 
comments.  I don't know how popular it is, but some people use these 
kind of comments:

/*---------.
| %param.  |
`---------*/

Here we want the vertical bar ("|") to be indented at the same column as 
the first "/".

Currently the result is this:

/*---------.
  | %param.  |
  `---------*/

This patch is a just proof of concept.  If this new behavior is indeed 
wanted, I would clean it up and adapt other modes.

[0001-c-ts-mode-Add-indentation-rule-for-else_clause.patch (text/x-patch, attachment)]

[0002-c-ts-mode-handle-specific-comment-formatting.patch (text/x-patch, attachment)]

Message #11 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Augustin Chéneau (BTuin) <btuin <at> mailo.com>, Yuan Fu
 <casouri <at> gmail.com>
Cc: 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Fri, 29 Sep 2023 10:17:29 +0300

> Date: Tue, 26 Sep 2023 14:29:07 +0200
> From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
> 
> I found some more issues.
> 
> First, there is no rule for an element in an else clause:
> 
> 
> if (true)
>    do_something();
> else
> do_something_else();
> 
> 
> "do_something_else" is not indented.
> 
> There is also something weird with the bsd indent style.  It indents 
> do_something and do_something_else to parent-bol with 0 offset, so the 
> result is:
> 
> if (true)
> do_something();
> else
> do_something_else();
> 
> 
> It is very different from the bsd style from c-mode, which produces this:
> 
> if (true)
> 	do_something();
> else
> 	do_something_else();
> 
> By looking at random files from OpenBSD, they do indent their 
> expressions inside if and else:
> 
> <https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/net/bsd-comp.c?rev=1.17&content-type=text/plain>
> (lines 277, 484, and 527)
> 
> 
> 
> Also there is a second patch which tries to handle specific types of 
> comments.  I don't know how popular it is, but some people use these 
> kind of comments:
> 
> /*---------.
> | %param.  |
> `---------*/
> 
> Here we want the vertical bar ("|") to be indented at the same column as 
> the first "/".
> 
> Currently the result is this:
> 
> /*---------.
>    | %param.  |
>    `---------*/
> 
> This patch is a just proof of concept.  If this new behavior is indeed 
> wanted, I would clean it up and adapt other modes.

Yuan, any comments?  If the first patch looks good to you, I'd like to
install it on the release branch.

Message #16 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: casouri <at> gmail.com
Cc: btuin <at> mailo.com, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Thu, 05 Oct 2023 10:16:45 +0300

Ping!  Yuan, I would really like to use the first patch in Emacs 29.2,
if it looks OK to you.

> Cc: 66152 <at> debbugs.gnu.org
> Date: Fri, 29 Sep 2023 10:17:29 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Tue, 26 Sep 2023 14:29:07 +0200
> > From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
> > 
> > I found some more issues.
> > 
> > First, there is no rule for an element in an else clause:
> > 
> > 
> > if (true)
> >    do_something();
> > else
> > do_something_else();
> > 
> > 
> > "do_something_else" is not indented.
> > 
> > There is also something weird with the bsd indent style.  It indents 
> > do_something and do_something_else to parent-bol with 0 offset, so the 
> > result is:
> > 
> > if (true)
> > do_something();
> > else
> > do_something_else();
> > 
> > 
> > It is very different from the bsd style from c-mode, which produces this:
> > 
> > if (true)
> > 	do_something();
> > else
> > 	do_something_else();
> > 
> > By looking at random files from OpenBSD, they do indent their 
> > expressions inside if and else:
> > 
> > <https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/net/bsd-comp.c?rev=1.17&content-type=text/plain>
> > (lines 277, 484, and 527)
> > 
> > 
> > 
> > Also there is a second patch which tries to handle specific types of 
> > comments.  I don't know how popular it is, but some people use these 
> > kind of comments:
> > 
> > /*---------.
> > | %param.  |
> > `---------*/
> > 
> > Here we want the vertical bar ("|") to be indented at the same column as 
> > the first "/".
> > 
> > Currently the result is this:
> > 
> > /*---------.
> >    | %param.  |
> >    `---------*/
> > 
> > This patch is a just proof of concept.  If this new behavior is indeed 
> > wanted, I would clean it up and adapt other modes.
> 
> Yuan, any comments?  If the first patch looks good to you, I'd like to
> install it on the release branch.
> 
> 
> 
> 

Message #19 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Yuan Fu <casouri <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: btuin <at> mailo.com, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sun, 10 Dec 2023 18:16:49 -0800

On 10/5/23 12:16 AM, Eli Zaretskii wrote:
> Ping!  Yuan, I would really like to use the first patch in Emacs 29.2,
> if it looks OK to you.
>
>> Cc: 66152 <at> debbugs.gnu.org
>> Date: Fri, 29 Sep 2023 10:17:29 +0300
>> From: Eli Zaretskii <eliz <at> gnu.org>
>>
>>> Date: Tue, 26 Sep 2023 14:29:07 +0200
>>> From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
>>>
>>> I found some more issues.
>>>
>>> First, there is no rule for an element in an else clause:
>>>
>>>
>>> if (true)
>>>     do_something();
>>> else
>>> do_something_else();
>>>
>>>
>>> "do_something_else" is not indented.
>>>
>>> There is also something weird with the bsd indent style.  It indents
>>> do_something and do_something_else to parent-bol with 0 offset, so the
>>> result is:
>>>
>>> if (true)
>>> do_something();
>>> else
>>> do_something_else();
>>>
>>>
>>> It is very different from the bsd style from c-mode, which produces this:
>>>
>>> if (true)
>>> 	do_something();
>>> else
>>> 	do_something_else();
>>>
>>> By looking at random files from OpenBSD, they do indent their
>>> expressions inside if and else:
>>>
>>> <https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/net/bsd-comp.c?rev=1.17&content-type=text/plain>
>>> (lines 277, 484, and 527)
>>>
>>>
>>>
>>> Also there is a second patch which tries to handle specific types of
>>> comments.  I don't know how popular it is, but some people use these
>>> kind of comments:
>>>
>>> /*---------.
>>> | %param.  |
>>> `---------*/
>>>
>>> Here we want the vertical bar ("|") to be indented at the same column as
>>> the first "/".
>>>
>>> Currently the result is this:
>>>
>>> /*---------.
>>>     | %param.  |
>>>     `---------*/
>>>
>>> This patch is a just proof of concept.  If this new behavior is indeed
>>> wanted, I would clean it up and adapt other modes.
>> Yuan, any comments?  If the first patch looks good to you, I'd like to
>> install it on the release branch.
LGTM, I applied the first patch to emacs-29.

Yuan

Message #22 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Yuan Fu <casouri <at> gmail.com>
To: Augustin Chéneau (BTuin) <btuin <at> mailo.com>,
 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sun, 10 Dec 2023 18:41:35 -0800

On 9/26/23 5:29 AM, Augustin Chéneau (BTuin) wrote:
> I found some more issues.
>
> First, there is no rule for an element in an else clause:
>
>
> if (true)
>   do_something();
> else
> do_something_else();
>
>
> "do_something_else" is not indented.

Right. tree-sitter-c recently changed their grammar and added 
else_clause. The fix for this is pushed to emacs-29 a few days ago.

>
> There is also something weird with the bsd indent style.  It indents 
> do_something and do_something_else to parent-bol with 0 offset, so the 
> result is:
>
> if (true)
> do_something();
> else
> do_something_else();
>
>
> It is very different from the bsd style from c-mode, which produces this:
>
> if (true)
>     do_something();
> else
>     do_something_else();
>
> By looking at random files from OpenBSD, they do indent their 
> expressions inside if and else:
>
> <https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/net/bsd-comp.c?rev=1.17&content-type=text/plain> 
>
> (lines 277, 484, and 527)
>
Thanks for reporting this, probably not a lot of people use c-ts-mode 
with bsd style, and things like this goes under the radar. I pushed a 
fix for it.

>
> Also there is a second patch which tries to handle specific types of 
> comments.  I don't know how popular it is, but some people use these 
> kind of comments:
>
> /*---------.
> | %param.  |
> `---------*/
>
> Here we want the vertical bar ("|") to be indented at the same column 
> as the first "/".
>
> Currently the result is this:
>
> /*---------.
>   | %param.  |
>   `---------*/
>
> This patch is a just proof of concept.  If this new behavior is indeed 
> wanted, I would clean it up and adapt other modes.

The gallery of artisan C comments is just endless :-) If we can support 
this style, it's definitely good, the only thing to watch out for is 
that the rules could unintentionally match some other comments that 
aren't really this style. Like, does people do this:

/*
 |
 |
 |
 */

in the wild? I don't know, maybe we need a embedded gpt-4 for formatting 
comments.

Yuan

Message #25 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Yuan Fu <casouri <at> gmail.com>
Cc: btuin <at> mailo.com, Eli Zaretskii <eliz <at> gnu.org>, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Wed, 10 Jan 2024 13:31:37 -0800

Yuan Fu <casouri <at> gmail.com> writes:

> LGTM, I applied the first patch to emacs-29.

What about patch 2 and 3?  Should they be installed on master?

Message #28 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: btuin <at> mailo.com, casouri <at> gmail.com, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Thu, 11 Jan 2024 08:24:43 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Wed, 10 Jan 2024 13:31:37 -0800
> Cc: Eli Zaretskii <eliz <at> gnu.org>, btuin <at> mailo.com, 66152 <at> debbugs.gnu.org
> 
> Yuan Fu <casouri <at> gmail.com> writes:
> 
> > LGTM, I applied the first patch to emacs-29.
> 
> What about patch 2 and 3?  Should they be installed on master?

Not sure.  It sounded like they were experimental, and no consensus
was reached.

Message #33 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Yuan Fu <casouri <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: btuin <at> mailo.com, 66152 <at> debbugs.gnu.org,
 Stefan Kangas <stefankangas <at> gmail.com>
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Fri, 12 Jan 2024 23:07:30 -0800

> On Jan 10, 2024, at 10:24 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
>> From: Stefan Kangas <stefankangas <at> gmail.com>
>> Date: Wed, 10 Jan 2024 13:31:37 -0800
>> Cc: Eli Zaretskii <eliz <at> gnu.org>, btuin <at> mailo.com, 66152 <at> debbugs.gnu.org
>> 
>> Yuan Fu <casouri <at> gmail.com> writes:
>> 
>>> LGTM, I applied the first patch to emacs-29.
>> 
>> What about patch 2 and 3?  Should they be installed on master?
> 
> Not sure.  It sounded like they were experimental, and no consensus
> was reached.

I had a look again, the first patch is applied, the second patch is fixed in another report, 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.

Yuan

Message #36 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Yuan Fu <casouri <at> gmail.com>
Cc: btuin <at> mailo.com, Eli Zaretskii <eliz <at> gnu.org>, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sat, 13 Jan 2024 23:33:05 -0600

Yuan Fu <casouri <at> 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?

Message #39 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: btuin <at> mailo.com, casouri <at> gmail.com, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sun, 14 Jan 2024 09:09:39 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Sat, 13 Jan 2024 23:33:05 -0600
> Cc: Eli Zaretskii <eliz <at> gnu.org>, btuin <at> mailo.com, 66152 <at> debbugs.gnu.org
> 
> Yuan Fu <casouri <at> gmail.com> writes:
> 
> > 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?

IMO, it would be nice to be able to support box comments.  I've seen
it in the wild enough to know that some people prefer this style.

Message #42 received at 66152 <at> debbugs.gnu.org (full text, mbox):

From: Augustin Chéneau (BTuin) <btuin <at> mailo.com>
To: Stefan Kangas <stefankangas <at> gmail.com>, Yuan Fu <casouri <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 66152 <at> debbugs.gnu.org
Subject: Re: bug#66152: 30.0.50; Missing indent rules in c-ts-mode
Date: Sun, 14 Jan 2024 11:21:48 +0100

Le 14/01/2024 à 06:33, Stefan Kangas a écrit :
> Yuan Fu <casouri <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.