From: Dmitry Gutov <dgutov@yandex.ru>
To: 61369@debbugs.gnu.org
Subject: bug#61369: Problem with keeping tree-sitter parse tree up-to-date
Date: Wed, 8 Feb 2023 17:34:25 +0200 [thread overview]
Message-ID: <fa9dd374-3840-c4ae-6e49-fdb5b7be08ba@yandex.ru> (raw)
1. Have some buffer with text
"use std::Path::{self, Path, PathBuf}; // good: std is a crate name
... (maybe something else
"
2. Have this text in a different buffer (I used scratch):
"
let date = DateTime::<chrono::Utc>::from_utc(date, chrono::Utc);
"
Meaning, the buffer starts with two empty lines.
3. Select the first line from the first buffer including the trailing
newline, yank and then paste at the beginning of the second buffer.
The second buffer will now look like this:
"use std::Path::{self, Path, PathBuf}; // good: std is a crate name
let date = DateTime::<chrono::Utc>::from_utc(date, chrono::Utc);
"
The parse tree will, however, be (according to treesit-explore-mode):
(source_file
(use_declaration use
argument:
(scoped_use_list
path: (scoped_identifier path: (identifier) :: name: (identifier))
::
list: (use_list { (self) , (identifier) , (identifier) }))
;)
(line_comment)
(let_declaration let pattern: (identifier) =
value:
(scoped_identifier
path:
(generic_type type: (type_identifier) ::
type_arguments:
(type_arguments <
(scoped_type_identifier path: (identifier) :: name:
(type_identifier))
>))
:: name: (identifier))
(ERROR ( (identifier) ,
(scoped_identifier path: (identifier) :: name: (identifier))
;)
;))
But if I edit the buffer after that, e.g. add and remove a space at the
beginning, the error node disappears:
(source_file
(use_declaration use
argument:
(scoped_use_list
path: (scoped_identifier path: (identifier) :: name: (identifier))
::
list: (use_list { (self) , (identifier) , (identifier) }))
;)
(line_comment)
(let_declaration let pattern: (identifier) =
value:
(call_expression
function:
(scoped_identifier
path:
(generic_type type: (type_identifier) ::
type_arguments:
(type_arguments <
(scoped_type_identifier path: (identifier) :: name:
(type_identifier))
>))
:: name: (identifier))
arguments:
(arguments ( (identifier) ,
(scoped_identifier path: (identifier) :: name: (identifier))
)))
;))
next reply other threads:[~2023-02-08 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:34 Dmitry Gutov [this message]
2023-02-08 18:20 ` bug#61369: Problem with keeping tree-sitter parse tree up-to-date Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 19:41 ` Dmitry Gutov
2023-02-10 1:22 ` Yuan Fu
2023-02-10 1:38 ` Dmitry Gutov
2023-02-13 9:10 ` Yuan Fu
2023-02-13 23:59 ` Yuan Fu
2023-02-15 2:17 ` Dmitry Gutov
2023-02-15 22:44 ` Dmitry Gutov
2023-02-17 22:32 ` Yuan Fu
2023-02-18 0:11 ` Dmitry Gutov
2023-02-18 1:14 ` Yuan Fu
2023-02-18 1:25 ` Dmitry Gutov
2023-02-18 10:05 ` Yuan Fu
2023-02-18 7:15 ` Eli Zaretskii
2023-02-18 17:21 ` Dmitry Gutov
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=fa9dd374-3840-c4ae-6e49-fdb5b7be08ba@yandex.ru \
--to=dgutov@yandex.ru \
--cc=61369@debbugs.gnu.org \
/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).