From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 30132@debbugs.gnu.org, 15998@debbugs.gnu.org,
Noam Postavsky <npostavs@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Shigeru Fukaya <shigeru.fukaya@gmail.com>
Subject: bug#30132: 27.0.50; scan-sexps and ##
Date: Sat, 07 May 2022 12:17:32 +0200 [thread overview]
Message-ID: <87h761ve83.fsf@gnus.org> (raw)
In-Reply-To: <875ymihtsc.fsf@web.de> (Michael Heerdegen's message of "Sat, 07 May 2022 06:05:07 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Dunno how the Edebug tests are supposed to run...: When I load
> edebug-tests.el and run those tests with M-x ert-run-tests-interactively
> t RET, I always get lots of fails - also with what is installed now (and
> even without the patch).
I run them with "make check" or "make edebug-tests".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-07 10:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 14:45 bug#15998: 24.3; forward-sexp (scan-sexps) doesn't do well with some SEXPs Shigeru Fukaya
2013-11-29 17:12 ` Stefan Monnier
2013-12-01 20:08 ` Shigeru Fukaya
2013-12-01 20:44 ` Stefan Monnier
2013-12-03 9:47 ` Shigeru Fukaya
2013-12-03 17:09 ` Stefan Monnier
2019-06-26 15:23 ` Lars Ingebrigtsen
2019-06-26 17:06 ` Stefan Monnier
2019-06-27 10:30 ` Lars Ingebrigtsen
2019-07-07 2:08 ` Noam Postavsky
2019-07-07 13:28 ` Stefan Monnier
2019-07-07 13:47 ` Noam Postavsky
2022-05-06 15:50 ` bug#30132: 27.0.50; scan-sexps and ## Lars Ingebrigtsen
2022-05-06 16:30 ` bug#15998: " Lars Ingebrigtsen
2022-05-07 0:08 ` Michael Heerdegen
2022-05-07 4:05 ` bug#15998: " Michael Heerdegen
2022-05-07 10:17 ` Lars Ingebrigtsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-15 18:09 Michael Heerdegen
2018-02-12 16:12 ` Michael Heerdegen
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=87h761ve83.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=15998@debbugs.gnu.org \
--cc=30132@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=shigeru.fukaya@gmail.com \
/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).