From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Gemini Lasswell <gazally@runbox.com>, 28747@debbugs.gnu.org
Subject: bug#28747: 26.0.60; Usage of "&rest body" in Edebug specs
Date: Sun, 01 May 2022 10:49:00 +0200 [thread overview]
Message-ID: <874k29tz7n.fsf@gnus.org> (raw)
In-Reply-To: <87v8y038yl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 31 Jan 2022 04:00:50 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Your point about &optional also makes me lean towards not doing anything
> here -- I mean, "&optional body" and "&rest body" are both likely in
> edebug specs, and the confusion here more stems from `body' in itself
> being nullable, I think?
>
> So I dunno whether renaming &rest to &repeat is going to help people
> that write debug specs in practice much.
I think the conclusion here is that we should probably let sleeping dogs
doze, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-05-01 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 15:02 bug#28747: 26.0.60; Usage of "&rest body" in Edebug specs Gemini Lasswell
2017-10-13 0:54 ` Noam Postavsky
2019-10-16 2:45 ` Lars Ingebrigtsen
2019-10-18 3:12 ` Richard Stallman
2019-10-18 3:35 ` Lars Ingebrigtsen
2019-10-18 14:14 ` Richard Stallman
2019-10-19 8:20 ` Lars Ingebrigtsen
2019-10-19 14:02 ` Michael Heerdegen
2022-01-29 15:56 ` Lars Ingebrigtsen
2022-02-01 5:03 ` Richard Stallman
2022-01-29 23:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-31 2:21 ` Lars Ingebrigtsen
2022-01-31 2:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-31 2:35 ` Lars Ingebrigtsen
2022-01-31 2:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-31 3:00 ` Lars Ingebrigtsen
2022-05-01 8:49 ` Lars Ingebrigtsen [this message]
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=874k29tz7n.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=28747@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=monnier@iro.umontreal.ca \
/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).