From: "João Távora" <joaotavora@gmail.com>
To: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
Cc: Yuan Fu <casouri@gmail.com>,
Theodor Thornhill <theo@thornhill.no>,
62412@debbugs.gnu.org
Subject: bug#62412: 29.0.60; strange c++ indentation behavior with tree sitter
Date: Sat, 25 Mar 2023 17:53:23 +0000 [thread overview]
Message-ID: <CALDnm52-05q1KuBb-5-HCGzob+qzcN=4hZN9iLgBMb-tbaQ7Eg@mail.gmail.com> (raw)
In-Reply-To: <a02af479-7b7c-98a6-c373-a52b960d215d@gmail.com>
On Sat, Mar 25, 2023 at 5:47 PM Herman, Géza <geza.herman@gmail.com> wrote:
> So if the aim is that the two c++ modes
> should work similarly out of the box, then it'd make sense to keep
> electric-indent-chars as is.
Only _if_ it is generally understood that c++-ts-mode's heuristics are
worse. And only _then_ if they can somehow fixed to become better.
Until these conditions are satisfied, I think electric-indent-chars
has to be left alone.
João
next prev parent reply other threads:[~2023-03-25 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 20:43 bug#62412: 29.0.60; strange c++ indentation behavior with tree sitter Herman, Geza
2023-03-24 18:17 ` Yuan Fu
2023-03-24 20:04 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-25 8:53 ` João Távora
2023-03-25 10:19 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-25 10:28 ` João Távora
2023-03-25 10:26 ` Herman, Géza
2023-03-25 11:43 ` João Távora
2023-03-25 13:48 ` Herman, Géza
2023-03-25 16:23 ` João Távora
2023-03-25 17:41 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 0:03 ` Stefan Kangas
2023-03-25 17:47 ` Herman, Géza
2023-03-25 17:53 ` João Távora [this message]
2023-03-26 13:54 ` Herman, Géza
2023-03-26 13:25 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CALDnm52-05q1KuBb-5-HCGzob+qzcN=4hZN9iLgBMb-tbaQ7Eg@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=62412@debbugs.gnu.org \
--cc=Herman@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=geza.herman@gmail.com \
--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 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).