unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 23, Python, epylint, pylint
Date: Mon, 02 Nov 2009 14:29:11 +0100	[thread overview]
Message-ID: <hcmmr8$o2k$1@ger.gmane.org> (raw)
In-Reply-To: 87ws2ahww9.fsf@liv.ac.uk

Dave Love <fx@domain.invalid> writes:

> Richard Riley <rileyrgdev@gmail.com> writes:
>
>> A more careful read of the flymake wiki page 
>>
>> Http://www.emacswiki.org/emacs/FlyMake
>>
>> Provided the answer:
>>
>> http://paste.lisp.org/display/60617
>
> [Gross code elided.]
>
> What's wrong with just adding this to `post-command-hook'?
>
>   (defun my-flymake-show-help ()
>     (when (get-char-property (point) 'flymake-overlay)
>       (let ((help (get-char-property (point) 'help-echo)))
>         (if help (message "%s" help)))))
>

Yes, adding that as a post-command-hook worked well. There was similar
code on the wiki but rather using wrappers for
flymake-goto-next-error. I like the errors to appear when I cursor over
the error in "live editing" mode so your solution is better for me. Wiki
updated.

thanks

r.





  parent reply	other threads:[~2009-11-02 13:29 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
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 [this message]
     [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='hcmmr8$o2k$1@ger.gmane.org' \
    --to=rileyrgdev@gmail.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).