From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: m h Newsgroups: gmane.emacs.devel Subject: Re: code coverage mode? Date: Thu, 22 Oct 2009 10:17:15 -0600 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1256229925 22107 80.91.229.12 (22 Oct 2009 16:45:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Oct 2009 16:45:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 22 18:45:14 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N10mo-0000rg-7H for ged-emacs-devel@m.gmane.org; Thu, 22 Oct 2009 18:45:14 +0200 Original-Received: from localhost ([127.0.0.1]:44187 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N10mn-00068D-Qr for ged-emacs-devel@m.gmane.org; Thu, 22 Oct 2009 12:45:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N10Lq-0003A6-Uk for emacs-devel@gnu.org; Thu, 22 Oct 2009 12:17:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N10Lm-000388-9K for emacs-devel@gnu.org; Thu, 22 Oct 2009 12:17:22 -0400 Original-Received: from [199.232.76.173] (port=54388 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N10Lm-000382-3Y for emacs-devel@gnu.org; Thu, 22 Oct 2009 12:17:18 -0400 Original-Received: from mail-vw0-f183.google.com ([209.85.212.183]:47167) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N10Ll-0007FH-HV for emacs-devel@gnu.org; Thu, 22 Oct 2009 12:17:17 -0400 Original-Received: by vws13 with SMTP id 13so3405969vws.14 for ; Thu, 22 Oct 2009 09:17:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Cqs4vZPvHUUWWLIf5qYsEGA76DjP97n3kN5t1clgGb4=; b=ozj3Q0zI534oeDKWiPvBjaQKeYLoea8BgXPkoNqJ/yEfDpxxffrDOcl5U4/knmV1ly Ol0CwxHmqKla7EPD2pePTC0g0xvZm2Pubtatuws/paj2kBFHvz4sl4at9S/tL7OgeK8K l4ETal7tUHajnNjKr+tx03QLmgPVR5Mkea8O4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=w051cJEAnA5HQznDckS4gy/YjCLhkJYX88y2BjxKm1W3cadFmrjmWaahCj0km71dyI cnvh72eWD1Ooccmwfib+lX0PiqvxL24Oc0aR+HYU5VxJrI5PpjMpOJOoZOjzjOIHIOYT qpossFeq3CE7NyhDAYbVtmY96BEFZ4nOsPm6w= Original-Received: by 10.220.124.88 with SMTP id t24mr4566941vcr.67.1256228235130; Thu, 22 Oct 2009 09:17:15 -0700 (PDT) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116308 Archived-At: On Thu, Oct 22, 2009 at 9:48 AM, Stefan Monnier wrote: >> I like the flymake style, yet I still want to really use flymake for >> how it was intended. =A0(Plus I don't want to be re-running coverage > [...] >> by any means, I'm hacking stuff together here. =A0But if this were >> python then I'd create a subclass of flymake and use that for >> coverage, while still using the former for its normal use (syntax >> checking). > > So, IIUC you'd like to be able to use flymake in two different ways at > the same time in the same buffer? =A0It's probably not too difficult to > do, but will require changing flymake for that. > Yes I want normal flymake, then for code coverage I (think I) want to turn on coverage-mode which will analyze the coverage data and if the data is fresher than the file, show the coverage data as well. Then when one starts typing some new code (or a new line at least), disable coverage data because it's stale. This might seem weird but the workflow I'm trying to get is working on a particular function, analyze the coverage for it, and add tests to get full coverage. My helper utility provides me the ability to only run tests for that function rather than a whole suite, so I imagine I'd want a macro to run coverage-for-function. > Patches welcome, yes, they are ;)