[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs 23, Python, epylint, pylint

From: Richard Riley
Subject: Re: Emacs 23, Python, epylint, pylint
Date: Fri, 23 Oct 2009 15:35:57 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Anselm Helbig <address@hidden> writes:

> At Thu, 22 Oct 2009 03:48:39 +0200,
> Richard Riley <address@hidden> wrote:
>> Richard Riley <address@hidden> 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

The flymake-cursor extension is the best! I'm still wondering about the
design decision to only show the error if you hover the mouse however
:-; Since it only appears in a lisp paste bucket at the moment, I
duplicated it here

reply via email to

[Prev in Thread] Current Thread [Next in Thread]