unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 61374@debbugs.gnu.org, casouri@gmail.com, eliz@gnu.org, juri@linkov.net
Subject: bug#61374: 30.0.50; Wrong mark-sexp with tree-sitter
Date: Tue, 14 Feb 2023 09:50:49 +0100	[thread overview]
Message-ID: <20230214085049.m7whlcqtd2tgu57q@Ergus> (raw)
In-Reply-To: <1EA777E8-3C44-47E5-A4CB-F80F7BE15ABB@thornhill.no>

Hi:

Sorry to bother. Any progress on this? 

Best,
Ergus

On Thu, Feb 09, 2023 at 08:53:03PM +0100, Theodor Thornhill wrote:
>
>
>On 9 February 2023 18:47:29 CET, Juri Linkov <juri@linkov.net> wrote:
>>> This will happen in many places iirc.  I'm not saying it's unfixable,
>>> just that I need to think a little about it, and some expected examples
>>> would be nice.
>>
>>Would it be possible to make sexp navigation in c-ts-mode exactly
>>like it was in c-mode?  It's quite frustrating when after switching
>>to c-ts-mode sexp commands operate on different things.
>
>That should be the goal, yeah :)
>
>Theo





  reply	other threads:[~2023-02-14  8:50 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 [this message]
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
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=20230214085049.m7whlcqtd2tgu57q@Ergus \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61374@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --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).