From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31052@debbugs.gnu.org, Andy Moreton <andrewjmoreton@gmail.com>
Subject: bug#31052: 26.0.91; Improve documentation of inline-letevals
Date: Wed, 04 Apr 2018 21:12:21 -0400 [thread overview]
Message-ID: <jwvtvsqcvfs.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83y3i32hhp.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Apr 2018 17:06:42 +0300")
>> Also, while looking at inline-letevals in inline.el, I noticed that the
>> preceeding macros inline--leteval and inline--letlisteval mention the
>> wrong symbol name in their error messages:
>>
>> (defmacro inline--leteval (_var-exp &rest _body)
>> (declare (indent 1) (debug (sexp &rest body)))
>> (error "inline-letevals can only be used within define-inline"))
>>
>> (defmacro inline--letlisteval (_list &rest _body)
>> (declare (indent 1) (debug (sexp &rest body)))
>> (error "inline-letevals can only be used within define-inline"))
>>
>> Perhaps these typos can be fixed before the release.
>
> It's not too late for that, but I'm not sure this is a typo. It could
> be deliberate.
>
> Stefan, can you comment on this, please?
Good catch: these aren't typos!
The inline-letevals macro expands to calls to inline--leteval and
inline--letlisteval and it's easier to have those signal the error than
to make inline-letevals check whether we're within a define-inline.
The user is not supposed to use inline--leteval or inline--letlisteval
manually anywhere at all (as indicated by the "--" in their name), so if
those occur it's (presumably) because of an incorrect use of
inline-letevals.
I'll add a comment about it, to stop other people from trying to "fix" it.
Stefan
next prev parent reply other threads:[~2018-04-05 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 0:33 bug#31052: 26.0.91; Improve documentation of inline-letevals Gemini Lasswell
2018-04-04 6:45 ` Eli Zaretskii
2018-04-04 13:18 ` Andy Moreton
2018-04-04 14:06 ` Eli Zaretskii
2018-04-05 1:12 ` Stefan Monnier [this message]
2018-04-04 17:10 ` Gemini Lasswell
2018-04-05 9:54 ` Eli Zaretskii
2018-04-06 20:29 ` Gemini Lasswell
2020-08-22 15:59 ` Lars Ingebrigtsen
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=jwvtvsqcvfs.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=31052@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
/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).