emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#63487: closed (30.0.50; C-M-u does not work correctly in c-ts-mode)


From: GNU bug Tracking System
Subject: bug#63487: closed (30.0.50; C-M-u does not work correctly in c-ts-mode)
Date: Fri, 19 May 2023 07:24:01 +0000

Your message dated Fri, 19 May 2023 00:23:11 -0700
with message-id <089D7600-BFF2-45DB-8CEB-0583603D6063@gmail.com>
and subject line Re: bug#63487: 30.0.50; C-M-u does not work correctly in 
c-ts-mode
has caused the debbugs.gnu.org bug report #63487,
regarding 30.0.50; C-M-u does not work correctly in c-ts-mode
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
63487: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63487
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 30.0.50; C-M-u does not work correctly in c-ts-mode Date: Sat, 13 May 2023 19:37:39 +0200
Steps to reproduce:

emacs -Q
C-x b sample.c RET
M-x c-ts-mode
Write the following code:

int foo(int a, int b) {
  
}

With point inside the function, press C-M-u.

Actual result:

Emacs beeps and shows "At top level".

Expected result:

Point goes to the open { instead.



--- End Message ---
--- Begin Message --- Subject: Re: bug#63487: 30.0.50; C-M-u does not work correctly in c-ts-mode Date: Fri, 19 May 2023 00:23:11 -0700

> On May 18, 2023, at 4:12 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> Date: Sat, 13 May 2023 19:37:39 +0200
>> From:  Daniel Martín via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> 
>> Steps to reproduce:
>> 
>> emacs -Q
>> C-x b sample.c RET
>> M-x c-ts-mode
>> Write the following code:
>> 
>> int foo(int a, int b) {
>> 
>> }
>> 
>> With point inside the function, press C-M-u.
>> 
>> Actual result:
>> 
>> Emacs beeps and shows "At top level".
>> 
>> Expected result:
>> 
>> Point goes to the open { instead.
> 
> I hope Yuan will look into this soon.

Thanks for the report. This is due to treesit-forward-sexp not signaling 
scan-error when it should. I pushed a fix for it.

Yuan



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]