unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 25471@debbugs.gnu.org
Subject: bug#25471: 26.0.50; Edebug and Testcover give incorrect code coverage results for code that uses 'unknown
Date: Sat, 06 Feb 2021 12:29:35 +0100	[thread overview]
Message-ID: <87sg69cu3k.fsf@gnus.org> (raw)
In-Reply-To: <m28tq97538.fsf@rainbow.local> (Gemini Lasswell's message of "Tue, 17 Jan 2017 13:24:11 -0800")

Gemini Lasswell <gazally@runbox.com> writes:

> This could be very simply fixed by changing Edebug to use
> `edebug-unknown' instead. The other symbols currently used to record
> code coverage are `1value' and `ok-coverage', and they could be changed
> respectively to `testcover-1value' and `edebug-ok-coverage'. edebug.el
> and testcover.el still wouldn't be able to do code coverage on
> themselves, but they should then work for everybody else.

I've now done the renaming in testcover.el in Emacs 28, too, and the
test case seems to work the same as before, so I'm closing this bug
report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-02-06 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 21:24 bug#25471: 26.0.50; Edebug and Testcover give incorrect code coverage results for code that uses 'unknown Gemini Lasswell
2019-07-27 10:30 ` Lars Ingebrigtsen
2021-02-06 11:29 ` Lars Ingebrigtsen [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=87sg69cu3k.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25471@debbugs.gnu.org \
    --cc=gazally@runbox.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).