From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Anselm Helbig Newsgroups: gmane.emacs.help Subject: Re: Emacs 23, Python, epylint, pylint Date: Fri, 23 Oct 2009 13:50:07 +0200 Organization: Freie Universitaet Berlin Message-ID: <87ljj29vo0.wl%anselm.helbig+news2009@googlemail.com> References: NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1256301656 22719 80.91.229.12 (23 Oct 2009 12:40:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 23 Oct 2009 12:40:56 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Oct 23 14:40:49 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N1JRo-0002R1-Al for geh-help-gnu-emacs@m.gmane.org; Fri, 23 Oct 2009 14:40:48 +0200 Original-Received: from localhost ([127.0.0.1]:50889 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N1JRn-0004Gy-P7 for geh-help-gnu-emacs@m.gmane.org; Fri, 23 Oct 2009 08:40:47 -0400 Original-Path: news.stanford.edu!usenet.stanford.edu!fu-berlin.de!uni-berlin.de!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 33 Original-X-Trace: news.uni-berlin.de G074+2/vbGTu7EgPy5o5gAIbprbUtt8/9DEu0WsLAlYPoljc22Mn38JYCV Cancel-Lock: sha1:qiGDBDMJy92Mshc23mXqcvtX3eo= In-Reply-To: Mail-Followup-To: Anselm Helbig Original-Xref: news.stanford.edu gnu.emacs.help:174086 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:69168 Archived-At: At Thu, 22 Oct 2009 03:48:39 +0200, Richard Riley wrote: > > Richard Riley writes: > > > [...] > > > > And successfully have pylint and emacs highlighting errors in my .py > > files courtesy of flymake. The problem is that I can't see anywhere the > > actually error description. Can anyone help please? > > > > [...] > > OK, its done so that you need to (yuck!) hover your mouse over the > hilited error. Kind of in the face of keyboard driven emacs, but at > least one can see the error. If anyone has a patch/fix/advice on how to > change this to show the errors in a buffer and maybe next error/previous > error then that would be great. In fact pylint.el does something like > that but it would be nice in conjunction with the flymake dynamic code > checking and error hiliting. While looking for a solution to this very problem I found out about display-local-help, bound to `C-h .' here. Good enough for me, and no configuration necessary. 8-) HTH, Anselm -- Anselm Helbig mailto:anselm.helbig+news2009@googlemail.com