yuutayamada / flycheck-tip Goto Github PK

I bind it to C-c C-p to go back to previous errors, but it goes straight to the first error.

related to #12

There is no need to deprecate this library just because flycheck-pos-tip exists! This one is actually better than flycheck-pos-tip: because it uses popup, it works on both terminals and window-system Emacs.

Commit 40f0d9e added a call to s-join, a function in the s.el library. This dependency isn't properly handled by MELPA, and I don't see it brought up in any of the documentation.

I'm definitely no elisp or MELPA expert, but surely there's a way to add s.el to the dependencies? Might also help to update the documentation.

It would be very nice to have a stable version on MELPA Stable. The process is quite simple, basically making a GIT tag.

May be not an issue, though is there a (simple) way to show popup with errors concering current line?

I have disabled showing errors in echo area completely through (setq flycheck-display-errors-function nil) and now want to display it on demand via popup..

When activating verbose output:

(flycheck-tip-use-timer 'verbose)

I'm constantly having the following message in my echo area (while hovering on a line with error):

Error: (void-function flycheck-tip-display-current-line-error-message)

flycheck-tip-cycle stops moving to the next error after first round of browsing all errors. Sometimes I press too fast and it got stuck as well.

Hello,

When I use flycheck-tip to display popups if I move around in a section that is marked with an error the tooltip will continuously be redrawn as I move around or type. This can make performance slow as you type. Here is an example of what I mean:

Otherwise I've had great success with the plugin. Thank you for writing it.

If the current point is on the erroneous line, it should automatically show a tip after idle time (i.e. after 0.5 second). This is needed because after the point is on a current erroneous line, if we execute flycheck-tip-cycle or flycheck-tip-cycle-reverse, it moves the point the the next/previous error, and we have to execute the cycle commands again to get back to the current error.

for example

foo.py

x  = 1
y  = 2

(http://i.imgur.com/FAWvLNj.png)

for example, below code occurs error, but can not show by flycheck-tip

foo.sh

if
#
# ↓ there is a newline below