Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flycheck-pos-tip throws error in console emacs #4111

Closed
gigawhitlocks opened this issue Dec 8, 2015 · 12 comments
Closed

flycheck-pos-tip throws error in console emacs #4111

gigawhitlocks opened this issue Dec 8, 2015 · 12 comments

Comments

@gigawhitlocks
Copy link

When running Spacemacs in the console, Flycheck emits an error when the cursor is placed over a bug it has detected in code.

The error displayed is the following:
Flycheck error display error: (error Window system frame should be used)

This appears to emanate from the flycheck-pos-tip package, which I've excluded in my .spacemacs file to allow flycheck to work normally as a workaround, but this issue should probably be tracked down and either reported upstream and/or worked-around within Spacemacs so that this does not occur by default.

@StreakyCobra
Copy link
Contributor

If the package is excluded it shouldn't happen :-/ It's probably on our side.

@gigawhitlocks
Copy link
Author

flycheck-pos-tip is included by default. I merely excluded it in my personal config as a workaround (and wanted to document that for anyone who winds up here from Google)

@StreakyCobra
Copy link
Contributor

Oh sorry, I understood it was still happening after excluding it.

@gigawhitlocks
Copy link
Author

Nope, excluding the package fixed the issue. If the issue is happening upstream, fixing it from Spacemacs' perspective may be as simple as detecting whether the user is running emacs in console & not loading flycheck-pos-tip in that case.

@StreakyCobra
Copy link
Contributor

Yes I got it. I remember having seen a discussion about this somewhere, but I can't find it back right now.

@gigawhitlocks
Copy link
Author

Awesome, just wanted to be sure y'all were aware 👍

@CestDiego
Copy link
Contributor

There is a PR by @travisbhartwell that addresses this I think: #2652

@StreakyCobra
Copy link
Contributor

This issue "follows" a recent change in the library explained here: #2110 (comment)

@CestDiego It happens even when not in daemon mode, so it's not linked to this PR.

@lunaryorn It seems pos-tip doesn't support non-GUI frame and throws an error. Do we need to handle this on Spacemacs side, or is it better to solve it in flycheck-pos-tip directly? I suppose it's better to handle it in flycheck-pos-tip (or even pos-tip?) as in daemon mode there can be both Terminal & GUI on the same instance.

@swsnr
Copy link
Contributor

swsnr commented Dec 9, 2015

@StreakyCobra I think that flycheck-pos-tip should not fail on TTYs. I can't show a popup either, though, because pos-top is explicitly about GUI tooltips. And I don't want to use popup.el as fallback, lest I introduce all those display issues again that I hoped to fix by moving back to pos-tip.

I think it'd be best to fall back to the standard echo area display, but make the fallback customisable.

Please open an issue in flycheck-pos-tip.

@nixmaniack
Copy link
Contributor

Fallback to echo area is be better. On my remote ssh session where I don't have display, there as well I hit similar issue. I skipped using flycheck-pos-tip and added following for a workaround.

(setq flycheck-display-errors-function 'flycheck-display-error-messages-unless-error-list)

@StreakyCobra
Copy link
Contributor

Reported upstream: flycheck/flycheck-pos-tip#11

@StreakyCobra
Copy link
Contributor

This issue has been fixed upstream one hour ago, and the update will be available on MELPA in a few hours (3-4). Let us know if this is the problem still persist after the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants