flycheck / flycheck-popup-tip Goto Github PK

View Code? Open in Web Editor NEW

32.0 32.0 5.0 88 KB

Display Flycheck error messages using popup.el

License: GNU General Public License v3.0

Emacs Lisp 100.00%

elisp emacs flycheck flycheck-extension popup tooltip

flycheck-popup-tip's Introduction

https://www.flycheck.org

Modern on-the-fly syntax checking extension for GNU Emacs. Try it!

Getting Started

Flycheck is available for installation with package.el on NonGNU ELPA, MELPA Stable and MELPA.

You can install Flycheck with the following command:

M-x package-install [RET] flycheck [RET]

Finally add this to your Emacs config:

(global-flycheck-mode +1)

Alternatively, if you're into use-package you can do the following:

(use-package flycheck
  :ensure t
  :config
  (add-hook 'after-init-hook #'global-flycheck-mode))

Now you can start using any of the bundled checkers or install additional checkers.

For a more gentle introduction read the Installation instructions and go through Quickstart guide.

Getting Help

Please ask questions about Flycheck on Stack Exchange or in our Gitter chat, and report bugs to our issue tracker.

Contributing

We welcome all kinds of contributions, whether you write patches, open pull requests, write documentation, help others with Flycheck issues, or just tell other people about your experiences with Flycheck. Please take a look at our Contributor’s Guide for help and guidance about contributing to Flycheck.

Sponsoring

You can support financially the development of Flycheck and related packages via:

Open Collective Backers

Open Collective Sponsors

Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]

Code of Conduct

We strive to create a safe, friendly and welcoming environment in the Flycheck community and have a Code of Conduct that defines acceptable and welcome behaviour as well as sanctions for violations. All contributors and all participants are expected to follow it, on Github, Gitter, Emacs.SX or any other place that’s part of Flycheck’s broader community.

License

Flycheck is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Flycheck is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

flycheck-popup-tip's People

Contributors

Stargazers

Watchers

Forkers

emacsmirror rubythonode lwiechec anonimitoraf lthms

flycheck-popup-tip's Issues

Conflicts with Lsp-mode

Hello,

I thought I would add this comment here after (finally) figuring out why Emacs would sometimes soft-hang at 100% CPU when hovering over /some/ flycheck errors-hints in a terminal:

This only happens towards the end of the buffer, e.g., if there is an error on the last line and you hover over it, Emacs will freeze.
This is due to some conflict with displaying TUI tooltips when both lsp-ui and flycheck-popup-tip wants to display something.

I haven't really had time to dig into /why/ this happens, and eventually I just concluded that lsp-ui essentially supersedes flycheck-popup-tip anyways so I will just be using that. But, if this occurs to you, now you might now why and have an inkling of how to proceed.

[Bug] "flycheck-popup-tip" messed up "display-line-numbers-mode"

While flycheck-popup-tip works perfect with linum-mode, it adds many new line numbers when display-line-numbers-mode is enabled (see below).

Before showing flycheck-popup-tip:

After showing flycheck-popup-tip:

The Popup clears the selection mark when selecting text with errors

When selecting text in emacs by holding the SHIFT key and moving my cursor around with the ARROW keys, if I step on a word highlighted by flycheck, it will open the popup with the error message, clearing my selection at the same time.

This is particularly infuriating when trying to fix errors reported by flycheck when refactoring code, since selecting the offending piece of code, usually results in stepping on a flycheck error which clears the whole thing.

Steps to reproduce the behavior:

Open some file with flycheck errors
Position your cursor before an error
Hold SHIFT and move your cursor over the error, trying to select the area from before the error, to after the error.
Observe the selection being cut in the middle when the cursor was on the flycheck error.

I would expect that, when selecting code, the popup should not open, or if it must, it should not clear the selection.

evil selection disappear on cursor move

When in evil visual mode, moving on a symbol marked as warning/error will trigger the popup but return in normal mode, making impossible to select things with errors/warning

https://cl.ly/1U1a0b2n0Y0q

Installation instructions do not work

Hi, thanks for this package!

Just thought I'd mention your init.el installation instructions did not work for me. I had to manually enable flycheck-popup-tip-mode in every new buffer.

I am using Emacs 26.1, without x.

I managed to get it to work by using:

(with-eval-after-load 'flycheck
  (flycheck-popup-tip-mode))

instead of

(with-eval-after-load 'flycheck
  '(add-hook 'flycheck-mode-hook 'flycheck-popup-tip-mode))

Marking where point is, does not work

Bug
Write a .cs script with an error:

|XvoidX Foo() {
^
 \___ Cursor is |. Wait until flycheck-popup-tip shows up indicating an error
      and press C-space then C-e to highlight line

The end result is that the cursor moves to the end of the line (due to C-e), but doesn't mark. Disabling flycheck-popup-tip fixes this problem.

Edit

Moving the cursor to the left, leaving one space char "fixes" the issue.
Marking via C-space twice at the original position (in the diagram) "fixes" the issue.
Moving the cursor to the EOL (C-e) "fixes" the issue.

Add package to Melpa

@cpitclaudel, I'll like to bring this package in Melpa. flycheck-pos-tip doesn't work for me, I'm using Emacs mostly from TTY. Does it make sense to place to place it under Flycheck org? For me is the same, I'll support it anyway.

using as fallback in tty, when emacs daemon started graphically

I sometimes open emacsclient -nw after starting emacs daemon with the GUI, in which case the tip about (if (display-graphic-p)… doesn't help, since it's only evaluated on daemon startup. This however seems to work:

  (setq flycheck-pos-tip-display-errors-tty-function #'flycheck-popup-tip-show-popup)
  (flycheck-pos-tip-mode)