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

On OSX flycheck messages show up on the monitor where the cursor is #4595

Closed
carloscheddar opened this issue Jan 13, 2016 · 11 comments
Closed
Labels
Reported upstream stale marked as a stale issue/pr (usually by a bot) Syntax-checking Visual

Comments

@carloscheddar
Copy link

Using OSX flycheck popup messages for errors and warnings show up on the monitor that has the cursor instead of only displaying on top of the spacemacs window.

@StreakyCobra
Copy link
Contributor

What's your emacs version?

In Emacs < 24.4 this is a known behaviour. Either update Emacs or add flycheck-pos-tip to the dotspacemacs-excluded-packages list :-)

@StreakyCobra
Copy link
Contributor

Reference: flycheck/flycheck-pos-tip#6 (comment)

@carloscheddar
Copy link
Author

Thanks I'll check that out but my version is 24.5.1.

@StreakyCobra
Copy link
Contributor

Weird. It's known that the tooltip goes over all windows, but there is normally a hook that disable the tooltip when the focus is exited from Emacs.

Or maybe are you in a situation where Spacemacs has the focus and another window is overlapping it on a side?

@carloscheddar
Copy link
Author

In my case Emacs has the focus but the cursor is on the second monitor which makes the tooltip show up where the cursor is located. When emacs loses focus the tooltip disappears so that's working correctly.

@StreakyCobra
Copy link
Contributor

Oh, the mouse cursor, not the emacs cursor :-) Ok I got it.

This is probably an upstream issue, but let's ask @lunaryorn to be sure.

The package providing the tooltip is flycheck-pos-tip, but it's using another library (pos-tip) to show the tooltips, so I suppose it should be reported there.

@swsnr
Copy link
Contributor

swsnr commented Jan 13, 2016

It sure sounds like an upstream issue. I'd appreciate if you could report this issue to flycheck-pos-tip, lest I forget about it.

Thank you very much

@carloscheddar
Copy link
Author

Oh my bad I should've been more specific. Thanks for the help, I'll report there.

@StreakyCobra
Copy link
Contributor

@carloscheddar When you have done this, please put a link back here :-)

@carloscheddar
Copy link
Author

@StreakyCobra Here it is flycheck/flycheck-pos-tip#15

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reported upstream stale marked as a stale issue/pr (usually by a bot) Syntax-checking Visual
Projects
Upstream bugs
Reported, waiting
Development

No branches or pull requests

3 participants