-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
If the package is excluded it shouldn't happen :-/ It's probably on our side. |
|
Oh sorry, I understood it was still happening after excluding it. |
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 |
Yes I got it. I remember having seen a discussion about this somewhere, but I can't find it back right now. |
Awesome, just wanted to be sure y'all were aware 👍 |
There is a PR by @travisbhartwell that addresses this I think: #2652 |
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 |
@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. |
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.
|
Reported upstream: flycheck/flycheck-pos-tip#11 |
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. |
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.The text was updated successfully, but these errors were encountered: