From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Gabriele Nicolardi <gabriele@medialab.sissa.it>
Cc: 71777@debbugs.gnu.org
Subject: bug#71777: 29.4; sexp-at-point in latex-mode when sexp contains ";"
Date: Tue, 25 Jun 2024 22:52:51 +0100 [thread overview]
Message-ID: <87tthg1yh8.fsf@jeremybryant.net> (raw)
In-Reply-To: <bdc05dba-8106-40cb-9a58-7c5ae12a26a8@medialab.sissa.it> (Gabriele Nicolardi's message of "Tue, 25 Jun 2024 19:53:59 +0200")
Gabriele Nicolardi <gabriele@medialab.sissa.it> writes:
> Hi,
>
> I have this string expression in latex-mode:
>
> $K(U_1, V_1, x_1; t_2, x_2)$
>
> If the pointer is located on the opened "(" and I run "forward-sexp"
> it works and the
> pointer goes after the closed ")".
>
> But if, again, the pointer is located on the opened "(" and I evaluate
> "(sexp-at-point)" it returns nil.
>
> If I remove the ";" symbol from the expression it works and returns
> the sexp-at-point:
>
> $K(U_1, V_1, x_1 t_2, x_2)$
>
> Is it a bug?
>
> Best regards,
>
> Gabriele
>
>
> In GNU Emacs 29.4 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.20,
> cairo version 1.16.0) of 2024-06-24 built on lcy02-amd64-050
> Repository revision: 176061eb965cf945e7627ce87bb16ec5a03f8a4d
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12013000
> System Description: Ubuntu 20.04.6 LTS
>
> Important settings:
> value of $LANG: it_IT.UTF-8
> locale-coding-system: utf-8-unix
>
> Major mode: LaTeX
This suggests you are using the major mode from AUCTeX, rather than the
built-in latex-mode? Is this right?
next prev parent reply other threads:[~2024-06-25 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:53 bug#71777: 29.4; sexp-at-point in latex-mode when sexp contains ";" Gabriele Nicolardi
2024-06-25 21:52 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-25 22:51 ` Gabriele Nicolardi
2024-06-26 12:39 ` bug#71777: 29.4; sexp-at-point in latex-mode when sexp contains "; " Eli Zaretskii
2024-06-26 13:46 ` bug#71777: 29.4; sexp-at-point in latex-mode when sexp contains ";" Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 15:52 ` Gabriele Nicolardi
2024-06-26 20:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 20:18 ` Gabriele Nicolardi
2024-06-26 20:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 20:40 ` Gabriele Nicolardi
2024-06-26 21:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 21:14 ` Gabriele Nicolardi
2024-06-26 21:26 ` Gabriele Nicolardi
2024-06-26 22:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-27 6:01 ` Gabriele Nicolardi
2024-06-29 12:25 ` Eli Zaretskii
2024-06-26 19:43 ` Gabriele Nicolardi
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=87tthg1yh8.fsf@jeremybryant.net \
--to=bug-gnu-emacs@gnu.org \
--cc=71777@debbugs.gnu.org \
--cc=gabriele@medialab.sissa.it \
--cc=jb@jeremybryant.net \
/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).