From: Jim Porter <jporterbugs@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>, 62224@debbugs.gnu.org
Subject: bug#62224: 30.0.50: Emacs don't, start sends an erroneous error
Date: Thu, 16 Mar 2023 11:45:40 -0700 [thread overview]
Message-ID: <cc750f76-aba5-76d8-f913-a87a1c0a8457@gmail.com> (raw)
In-Reply-To: <628707db-561e-334d-dd98-38a56fa39586@easy-emacs.de>
On 3/16/2023 11:08 AM, Andreas Röhler wrote:
> Emacs don't start sending an erroneous error, backtrace at the end of
> this report.
>
> Error points to the docstring of the function below, notably at the
> escaped ‘x’:
>
> ---
> (defun lean-input-compose (f g)
> "\x -> concatMap F (G x)"
> (lexical-let ((f1 f) (g1 g))
> (lambda (x) (lean-input-concat-map f1 (funcall g1 x)))))
> ---
In Emacs Lisp, "\x" is the start of a hexadecimal character escape, like
"\x41" for "A". In Emacs 29, just a plain "\x" was treated as NUL, but
in Emacs 30, this is now a syntax error. I think that makes sense, since
it helps catch likely mistakes such as this one.
That said, I think *technically* the manual says that "\x" is allowed:
> You can use any number of hex digits, so you can represent any
> character code in this way.
Zero is a number, after all. :) Maybe the manual needs an update to be
more-precise here?
Ultimately, I think this is a bug in lean-mode though. I don't know
anything about Lean in particular, but I think the docstring above is
trying to use the backslash literally, rather than as an escape introducer.
next prev parent reply other threads:[~2023-03-16 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 18:08 bug#62224: 30.0.50: Emacs don't, start sends an erroneous error Andreas Röhler
2023-03-16 18:45 ` Jim Porter [this message]
2023-03-16 20:07 ` Eli Zaretskii
2023-03-16 20:31 ` Jim Porter
2023-03-18 8:10 ` Andreas Röhler
2023-03-18 8:33 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc750f76-aba5-76d8-f913-a87a1c0a8457@gmail.com \
--to=jporterbugs@gmail.com \
--cc=62224@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.