From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: gazally@runbox.com, 28747@debbugs.gnu.org
Subject: bug#28747: 26.0.60; Usage of "&rest body" in Edebug specs
Date: Fri, 18 Oct 2019 05:35:14 +0200 [thread overview]
Message-ID: <87r23ak9ot.fsf@gnus.org> (raw)
In-Reply-To: <E1iLIgS-0003jg-Je@fencepost.gnu.org> (Richard Stallman's message of "Thu, 17 Oct 2019 23:12:08 -0400")
Richard Stallman <rms@gnu.org> writes:
> > > The symbol &rest in an Edebug spec has a different meaning than it has
> > > in an argument list.
>
> That seems like a confusing wrinkle. Could we possibly change Emacs
> to smooth it out?
Yes, the suggestion was to make &repeat a synonym for &rest and then
replace all the usages.
I'm not sure this is worth the code churn, though -- as was pointed out,
virtually all the debug specs gets this right anyway. Does anybody have
an opinion?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-18 3:35 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 [this message]
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
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=87r23ak9ot.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=28747@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=rms@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 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.