From: Anselm Helbig <anselm.helbig+news2009@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 23, Python, epylint, pylint
Date: Fri, 23 Oct 2009 13:50:07 +0200 [thread overview]
Message-ID: <87ljj29vo0.wl%anselm.helbig+news2009@googlemail.com> (raw)
In-Reply-To: <mailman.9250.1256176158.2239.help-gnu-emacs@gnu.org>
At Thu, 22 Oct 2009 03:48:39 +0200,
Richard Riley <rileyrgdev@gmail.com> wrote:
>
> Richard Riley <rileyrgdev@gmail.com> 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
next prev parent reply other threads:[~2009-10-23 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 1:30 Emacs 23, Python, epylint, pylint Richard Riley
2009-10-22 1:48 ` Richard Riley
2009-10-22 2:10 ` Richard Riley
[not found] ` <mailman.9250.1256176158.2239.help-gnu-emacs@gnu.org>
2009-10-23 11:50 ` Anselm Helbig [this message]
2009-10-23 13:35 ` Richard Riley
[not found] ` <mailman.9306.1256304994.2239.help-gnu-emacs@gnu.org>
2009-11-01 19:23 ` Dave Love
2009-11-02 13:02 ` Richard Riley
2009-11-02 13:29 ` Richard Riley
[not found] <mailman.9249.1256175078.2239.help-gnu-emacs@gnu.org>
2009-11-01 19:22 ` Dave Love
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=87ljj29vo0.wl%anselm.helbig+news2009@googlemail.com \
--to=anselm.helbig+news2009@googlemail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).