[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65823: 30.0.50; sexp mismatches
From: |
Garjola Dindi |
Subject: |
bug#65823: 30.0.50; sexp mismatches |
Date: |
Wed, 20 Sep 2023 21:17:59 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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@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
--