From: Stefan Kangas <stefankangas@gmail.com>
To: "Augustin Chéneau" <btuin@mailo.com>
Cc: 66153-done@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#66153: 30.0.50; treesit: Edge case in indentation with multiple languages
Date: Sat, 30 Sep 2023 16:25:26 -0700 [thread overview]
Message-ID: <CADwFkmkJTKy645QeP0DQdK4qVyGmAF72gMQA9EMqL5wUARJ_nw@mail.gmail.com> (raw)
In-Reply-To: <fc4c9f67-f06e-44d4-9c02-32da06e97fe9@mailo.com> ("Augustin Chéneau (BTuin)"'s message of "Fri, 22 Sep 2023 13:27:00 +0200")
Version: 30.1
Augustin Chéneau (BTuin) <btuin@mailo.com> writes:
> There is an edge case in treesit with multiple languages
> indentation. Here is a simple example:
>
> // language_A
> {
> // language_B
> }
> // language_A
>
>
> Here, brackets are managed by language_A, but everything inside is
> managed by language_B. Meaning that if the pointer is at the beginning
> of the third line (with the closing bracket), it will use language_B's
> indent rules. But if the point is located on the bracket, it will use
> language_A's rules.
It seems like this patch was installed on master, but the bug was left
open in the bug tracker. I'm therefore closing it now.
Please remember to close bug reports when they are fixed.
commit 7447d3df94e49bef8577008d76a6b1f6a4013146
Author: Augustin Chéneau <btuin@mailo.com>
Commit: Yuan Fu <casouri@gmail.com>
Date: Wed Sep 20 12:23:22 2023 +0200
Fix tree-sitter indentation conflict with multiple languages
* lisp/treesit.el (treesit--indent-1): Use bol instead of point.
Copyright-paperwork-exempt: yes
prev parent reply other threads:[~2023-09-30 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 11:27 bug#66153: 30.0.50; treesit: Edge case in indentation with multiple languages Augustin Chéneau
2023-09-22 12:18 ` Dmitry Gutov
2023-09-30 23:25 ` Stefan Kangas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkJTKy645QeP0DQdK4qVyGmAF72gMQA9EMqL5wUARJ_nw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=66153-done@debbugs.gnu.org \
--cc=btuin@mailo.com \
--cc=casouri@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 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.