GNU bug report logs - #80141
Opening parenthesis chars in a list

Previous Next

Package: emacs;

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

Date: Tue, 6 Jan 2026 18:29:01 UTC

Severity: normal

To reply to this bug, email your comments to 80141 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#80141; Package emacs. (Tue, 06 Jan 2026 18:29:02 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. (Tue, 06 Jan 2026 18:29: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: Opening parenthesis chars in a list
Date: Tue, 6 Jan 2026 19:28:39 +0100

[Message part 1 (text/plain, inline)]
Elisp Info 2.4.3.1 Basic Char Syntax tells:

"you must add a backslash before any of the characters ‘()[]\;\"’"

Okay, because otherwise ‘parse-partial-sexp’ calculates wrong nesting 
WRT the listing below

(setq a (list ?())

(parse-partial-sexp (point-min) (point)) ==> (1 1 32 nil nil nil 0 nil 
nil (1) nil)

a => (40)

However, the problem also occurs with ‘?⁅’ and a couple of other characters.

Maybe tell ‘parse-partial-sexp’ not to consider any character following 
question mark as opening parenthesis?

Thanks,

Andreas

[Message part 2 (text/html, inline)]
This bug report was last modified 5 days ago.

Previous Next

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