From: Douglas Lewan <d.lewan2000@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Undefining an ERT test?
Date: Fri, 12 Jun 2020 02:51:46 -0400 [thread overview]
Message-ID: <bad18ff6-0208-2227-bb3d-7bdcfaa9e70f@gmail.com> (raw)
In-Reply-To: <87blloajg9.fsf@fastmail.fm>
On 6/12/20 2:26 AM, Joost Kremers wrote:
>
> You are right, `ert-delete-test` and `ert-delete-all-tests` should
> probably be in the documentation. I just checked the ERT docs that
> come with my Emacs 27 install and those two functions don't seem to be
> mentioned.
>
Thanks. I'll submit a bug when I get up and have a cllearer head.
--
,Doug
d.lewan2000@gmail.com
(908) 720 7908
If this is what winning looks like, I'd hate to see what losing is.
prev parent reply other threads:[~2020-06-12 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 21:52 Undefining an ERT test? Douglas Lewan
2020-06-11 22:10 ` Joost Kremers
2020-06-11 22:27 ` Douglas Lewan
2020-06-11 23:01 ` Joost Kremers
2020-06-11 23:22 ` Douglas Lewan
2020-06-11 23:37 ` Joost Kremers
2020-06-12 4:17 ` Douglas Lewan
2020-06-12 6:26 ` Joost Kremers
2020-06-12 6:51 ` Douglas Lewan [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=bad18ff6-0208-2227-bb3d-7bdcfaa9e70f@gmail.com \
--to=d.lewan2000@gmail.com \
--cc=help-gnu-emacs@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.
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).