From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 22471@debbugs.gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: bug#22471: ert batch should print compile parsable error messages
Date: Sun, 24 Oct 2021 14:57:40 +0200 [thread overview]
Message-ID: <871r4abmwr.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnChMB0b3S3i2Oqvr8K+vZpnYxnJE2CFUv9cWFYN+yOEg@mail.gmail.com> (Stefan Kangas's message of "Fri, 22 Oct 2021 17:15:35 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> I got the following backtrace, but gave up after looking at it for a
> while:
>
> Debugger entered--Lisp error: (error "Don’t know where
> ‘fns-tests-string-bytes’ is defin...")
> signal(error ("Don’t know where ‘fns-tests-string-bytes’ is defin..."))
Well -- ert-deftest doesn't record what file it's from, I think?
Looking at the definition, it just adds the test to the symbol-plist.
So that macro would also have to stash the file name somewhere.
load-history would be possible (but sounds unclean), so stashing it in
the symbol-plist would be better.
Then find-definition-noselect could be extended to use that for this
type.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-24 12:57 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r4abmwr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22471@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=stefan@marxist.se \
/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.