From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: code coverage mode? Date: Thu, 22 Oct 2009 11:48:23 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1256226545 9641 80.91.229.12 (22 Oct 2009 15:49:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Oct 2009 15:49:05 +0000 (UTC) Cc: emacs-devel@gnu.org To: m h Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 22 17:48:54 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 1N0zu4-0002Pw-M0 for ged-emacs-devel@m.gmane.org; Thu, 22 Oct 2009 17:48:40 +0200 Original-Received: from localhost ([127.0.0.1]:55445 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0zu3-0003Y7-U6 for ged-emacs-devel@m.gmane.org; Thu, 22 Oct 2009 11:48:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N0ztz-0003Xe-BY for emacs-devel@gnu.org; Thu, 22 Oct 2009 11:48:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N0ztu-0003Uv-Hq for emacs-devel@gnu.org; Thu, 22 Oct 2009 11:48:34 -0400 Original-Received: from [199.232.76.173] (port=57840 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0ztu-0003Ul-Eo for emacs-devel@gnu.org; Thu, 22 Oct 2009 11:48:30 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:17460 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N0ztu-0002s1-51 for emacs-devel@gnu.org; Thu, 22 Oct 2009 11:48:30 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ar0EAGIb4EpLd/m0/2dsb2JhbACBUto3hD8EiB0 X-IronPort-AV: E=Sophos;i="4.44,605,1249272000"; d="scan'208";a="47998296" Original-Received: from 75-119-249-180.dsl.teksavvy.com (HELO pastel.home) ([75.119.249.180]) by ironport2-out.pppoe.ca with ESMTP; 22 Oct 2009 11:48:29 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 538378074; Thu, 22 Oct 2009 11:48:23 -0400 (EDT) In-Reply-To: (m. h.'s message of "Thu, 22 Oct 2009 01:25:22 -0600") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:116307 Archived-At: > I like the flymake style, yet I still want to really use flymake for > how it was intended. (Plus I don't want to be re-running coverage [...] > by any means, I'm hacking stuff together here. But 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? It's probably not too difficult to do, but will require changing flymake for that. Patches welcome, Stefan