unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Garjola Dindi <garjola@garjola.net>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 65823@debbugs.gnu.org
Subject: bug#65823: 30.0.50; sexp mismatches
Date: Wed, 20 Sep 2023 21:17:59 +0200	[thread overview]
Message-ID: <87y1h0vel4.fsf@pc-117-162.gandi.net> (raw)
In-Reply-To: <1a95cfe1-49dd-37ce-a581-2ebcee4a381d@easy-emacs.de> ("Andreas Röhler"'s message of "Fri, 8 Sep 2023 16:01:27 +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@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
-- 





      reply	other threads:[~2023-09-20 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 14:01 bug#65823: 30.0.50; sexp mismatches Andreas Röhler
2023-09-20 19:17 ` Garjola Dindi [this message]

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=87y1h0vel4.fsf@pc-117-162.gandi.net \
    --to=garjola@garjola.net \
    --cc=65823@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    /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).