From: phillip.lord@russet.org.uk (Phillip Lord)
To: Glenn Morris <rgm@gnu.org>
Cc: 22471@debbugs.gnu.org
Subject: bug#22471: ert batch should print compile parsable error messages
Date: Thu, 28 Jan 2016 17:14:57 +0000 [thread overview]
Message-ID: <87lh79iq26.fsf@russet.org.uk> (raw)
In-Reply-To: <egmvrqa3wp.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 27 Jan 2016 20:28:22 -0500")
Glenn Morris <rgm@gnu.org> writes:
> Why would you call the batch version of ert from within Emacs,
> when M-x ert exists and does colour, hyperlinking to source, etc?
M-x ert is nice, but has one main failure. It's not running in a clean,
controllable Emacs; it's running in my Emacs. I use M-x ert only when I
am debugging failing tests.
The rest of the time, I run tests in a clean, newly launched Emacs with
a sandboxed .emacs.d/elpa. As a secondary advantage, it can be easier to
test two or three Emacs versions at the same time.
I've been writing a library to help get around this problem, but
fundamentally, the only clean way to test code is not to run it in the
same Emacs as is launching it. At some point, I'd like to add the
ability to launch an emacs for every test.
Phil
next prev parent reply other threads:[~2016-01-28 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:15 bug#22471: ert batch should print compile parsable error messages Phillip Lord
2016-01-27 16:06 ` Eli Zaretskii
2016-01-27 21:53 ` Phillip Lord
2016-01-28 1:28 ` Glenn Morris
2016-01-28 17:14 ` Phillip Lord [this message]
2020-08-20 16:39 ` Lars Ingebrigtsen
2020-08-20 16:51 ` Philipp Stephani
2021-10-23 0:15 ` Stefan Kangas
2021-10-24 12:57 ` Lars Ingebrigtsen
2021-10-24 14:27 ` Stefan Kangas
2021-10-24 20:01 ` Lars Ingebrigtsen
2022-01-24 12:54 ` 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=87lh79iq26.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=22471@debbugs.gnu.org \
--cc=rgm@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).