GNU bug report logs - #65823
30.0.50; sexp mismatches

Previous Next

Package: emacs;

Reported by: Andreas Röhler <andreas.roehler <at> easy-emacs.de>

Date: Fri, 8 Sep 2023 14:02:01 UTC

Severity: normal

Tags: confirmed

Found in version 30.0.50

To reply to this bug, email your comments to 65823 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#65823; Package emacs. (Fri, 08 Sep 2023 14:02:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Andreas Röhler <andreas.roehler <at> easy-emacs.de>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 08 Sep 2023 14:02:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.0.50; sexp mismatches
Date: Fri, 8 Sep 2023 16:01:27 +0200
;; Buffer in emacs-lisp-mode.

(defun foo (arg)
  "(Some command \"]\" )  ( "
  ;; ( asdf
  (interactive "p*")
  (message "%s" arg))

;; In example code above go into docstring at opening parenthesis from 
"(Some".
;; M-x forward-sexp RET will match the closing bracket, not the closing
;; parenthesis.

;; Also, when starting from closing parenthesis in docstring, it does 
not get
;; the opening.


;; Second:
;; With cursor at comment line, at open paren before asdf:

;; M-x forward-sexp RET matches the end of defun outside comment.
;; But from there backward-sexp doesn't reach the starting point.

;; Forward- and backward-sexp should correspond WRT of the position reached.

;; When sexp navigation starts from inside a string or comment, it
;; should match only in respective environment.

;; GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.33, cairo version 1.16.0) of 2023-09-08





Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#65823; Package emacs. (Wed, 20 Sep 2023 22:58:02 GMT) Full text and rfc822 format available.

Message #8 received at 65823 <at> debbugs.gnu.org (full text, mbox):

From: Garjola Dindi <garjola <at> garjola.net>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 65823 <at> debbugs.gnu.org
Subject: Re: bug#65823: 30.0.50; sexp mismatches
Date: Wed, 20 Sep 2023 21:17:59 +0200
Hi,

I confirm that I can reproduce this using

GNU Emacs 30.0.50 (build 7, x86_64-pc-linux-gnu, GTK+ Version 3.24.37,
cairo version 1.16.0) of 2023-09-16

Thanks.

Garjola

On Fri 08-Sep-2023 at 16:01:27 +02, Andreas Röhler
<andreas.roehler <at> easy-emacs.de> wrote: 
> ;; Buffer in emacs-lisp-mode.
>
> (defun foo (arg)
>   "(Some command \"]\" )  ( "
>   ;; ( asdf
>   (interactive "p*")
>   (message "%s" arg))
>
> ;; In example code above go into docstring at opening parenthesis from
>    "(Some".
> ;; M-x forward-sexp RET will match the closing bracket, not the closing
> ;; parenthesis.
>
> ;; Also, when starting from closing parenthesis in docstring, it does
>    not get
> ;; the opening.
>
>
> ;; Second:
> ;; With cursor at comment line, at open paren before asdf:
>
> ;; M-x forward-sexp RET matches the end of defun outside comment.
> ;; But from there backward-sexp doesn't reach the starting point.
>
> ;; Forward- and backward-sexp should correspond WRT of the position reached.
>
> ;; When sexp navigation starts from inside a string or comment, it
> ;; should match only in respective environment.
>
> ;; GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
>    3.24.33, cairo version 1.16.0) of 2023-09-08
-- 




Added tag(s) confirmed. Request was from Garjola Dindi <garjola <at> garjola.net> to control <at> debbugs.gnu.org. (Wed, 20 Sep 2023 22:58:03 GMT) Full text and rfc822 format available.

This bug report was last modified 1 year and 268 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.