From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: 61374@debbugs.gnu.org
Subject: bug#61374: 30.0.50; Wrong mark-sexp with tree-sitter
Date: Sun, 19 Feb 2023 07:22:58 +0100 [thread overview]
Message-ID: <6CD716B5-814C-4BC6-87A6-511A7C7F6293@thornhill.no> (raw)
In-Reply-To: <20230219021542.cfh7wkgzxrm3ki3h@Ergus>
On 19 February 2023 03:15:42 CET, Ergus <spacibba@aol.com> wrote:
>Hi Theo:
>
>I know you have multiple bug reports going on (actually some of them are
>all my fault ;p indeed) But this one with sexp is a very broken one
>IMHO, so I ping again ;).
>
>Did you finally got some time to think on this?
>
>Best,
>Ergus
>
>
>
>On Tue, Feb 14, 2023 at 11:50:56AM +0100, Theodor Thornhill wrote:
>> Ergus <spacibba@aol.com> writes:
>>
>>> Hi:
>>>
>>> Sorry to bother. Any progress on this?
>>>
>>
>> No problem! No, not yet. Will try to look at it tonight. Thanks for
>> reminding me :)
>>
>> Theo
No worries!
Yeah, I'm working on it, but it seems particularly hard with c for some reason. I haven't prioritized this lately as this code is in master, but the other fixes are on release branch.
I think I have a solution that will make the transition much easier, though. I'll see if I can make a proper attempt this evening.
Sorry :)
Theo
next prev parent reply other threads:[~2023-02-19 6:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875ycbitav.fsf.ref@aol.com>
2023-02-09 0:19 ` bug#61374: 30.0.50; Wrong mark-sexp with tree-sitter Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 6:40 ` Eli Zaretskii
2023-02-09 6:49 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 8:42 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 8:54 ` Eli Zaretskii
2023-02-09 9:41 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 10:52 ` Eli Zaretskii
2023-02-09 11:08 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 16:14 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 17:47 ` Juri Linkov
2023-02-09 19:53 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 8:50 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 10:50 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 2:15 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 6:22 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-03-20 20:19 ` Ergus 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=6CD716B5-814C-4BC6-87A6-511A7C7F6293@thornhill.no \
--to=bug-gnu-emacs@gnu.org \
--cc=61374@debbugs.gnu.org \
--cc=spacibba@aol.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).