Open vanceism7 opened 5 years ago
:thinking: I'm not sure which bugs you have in mind ^^ In any case, did you consider customizing flycheck-pos-tip-timeout?
(Also, it's not just guys around here)
Apparently there were some bugs a year or two back (I think) where the tooltip was staying on the screen even after the cursor left the error part of a line, or even when emacs didn't close I guess.
Anyways, it took me a while to find the settings where I could change the timeout, but I thought maybe not having a timeout might be a smarter default.
(And haha yea I meant "guys" like the blanket term for "everyone here". Kind of like how Spanish uses "Ellos" to address a group of men and women lol)
Anyways, it took me a while to find the settings where I could change the timeout, but I thought maybe not having a timeout might be a smarter default.
I can't think of other packages that don't have a timeout on tooltips, but I'm happy to hear @fmdkdd might think.
I don't even use pos-tip, but I can understand that the tooltip disappearing before you had time to read and understand the error can be frustrating.
I can't think of other packages that don't have a timeout on tooltips
In Emacs land I don't know, but Firefox doesn't seem to have a timeout on tooltips. Nor do Github various tooltips.
We are already dismissing the tooltip on focus-out and post-command. I don't know which bugs @vanceism7 has in mind either, but at the very least increasing the default timeout should be safe.
Hi all, I am coming here from Spacemacs, where flycheck-pos-tip is used (at least as part of haskell-layer, if not wider), and I am having a problem with popup disappearing after 5 seconds, making it mostly unusable -> I have to constantly move my cursor from and back to the error to see the rest of the message. I am wondering how to other users use it if it is so short?
From what I am getting, default timeout is 5 seconds, which is way too short from my perspective. I see discussion has been here to either make it longer, or to remove it. Are there any use cases which can explain why this timeout is needed at all? If no, then I would suggest removing it completely, at least as a default.
Hey guys, I know there's been some bugs in the past regarding the tooltip not disappearing, and that a timeout was added on the tooltip to manage this to some degree, but it seems like these past issues have been fixed, and I think it makes sense in general to not have a timeout on errors. This way, we're able to read through errors without having to continually re-trigger the error popup.
Hope this suggestion is agreeable to everyone! Thanks for all your work on this cool extension!