From: Bruce Stephens <bruce.stephens@isode.com>
To: Eli Zaretskii <eliz@gnu.org>, Theodor Thornhill <theo@thornhill.no>
Cc: casouri@gmail.com, 59686@debbugs.gnu.org
Subject: bug#59686: 30.0.50; tree-sitter indentation in some loops and conditional statements is wrong
Date: Fri, 2 Dec 2022 10:46:34 +0000 [thread overview]
Message-ID: <86268d17-402f-6ae3-9ed7-100a2591e04d@isode.com> (raw)
In-Reply-To: <83v8mufbd2.fsf@gnu.org>
On 02/12/2022 08:39, Eli Zaretskii wrote:
> FWIW, this is an unusual style, so I see no catastrophe if it is not 110%
> according to expectations. Users can easily fix that by tweaking their BOLs
> where important.
The example I gave would be unusual, I think, but I'd argue that the
situations where I saw the problem are quite natural.
For example,
} else if ( MYSTRCMP (attname, SOME_PREFIX_X400ADDRESS) ||
MYSTRCMP (attname, SOME_PREFIX_X400) ) {
FOO_ptr orp = foo_std2foo (val);
or a function declaration with several arguments with types that are
rather long.
I agree it's not a critical bug but if there's no appropriate general
fix it would be helpful to have some guidance for users to resolve our
specific cases.
next prev parent reply other threads:[~2022-12-02 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 18:41 bug#59686: 30.0.50; tree-sitter indentation in some loops and conditional statements is wrong Bruce Stephens
2022-12-02 5:13 ` Yuan Fu
2022-12-02 5:42 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-02 8:39 ` Eli Zaretskii
2022-12-02 9:20 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-02 10:46 ` Bruce Stephens [this message]
2022-12-02 11:51 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 10:48 ` Yuan Fu
2022-12-03 11:08 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-03 11:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86268d17-402f-6ae3-9ed7-100a2591e04d@isode.com \
--to=bruce.stephens@isode.com \
--cc=59686@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=theo@thornhill.no \
/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.