GNU bug report logs - #71777
29.4; sexp-at-point in latex-mode when sexp contains ";"

Previous Next

Full log

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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Gabriele Nicolardi <gabriele <at> medialab.sissa.it>, 71777 <at> debbugs.gnu.org
Subject: Re: bug#71777: 29.4; sexp-at-point in latex-mode when sexp contains
 ";"
Date: Wed, 26 Jun 2024 09:46:59 -0400

>> $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?
>
> I don't think it's a bug.  forward-sexp moves across balanced
> expressions, so it is not specific to Lisp.  By contrast,
> sexp-at-point is specific to Lisp and Lisp-like syntax, and so it uses
> the buffer's syntax.  Which is why ';' affects the result.
>
> Adding Stefan in case he has comments for this.

AFAICT, `sexp-at-point` correctly finds the parenthesized thingy, but it
is asked to return the Lisp object it represents rather than a string,
so it `read`s, which inevitably obeys the ELisp syntax.

IOW, I suspect you want (thing-at-point 'sexp) rather than
(sexp-at-point).


        Stefan

Previous Next

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