Disable hover in editor

[misantronic]

• VSCode Version: 1.9.0
• OS Version: macOS 10.12.2

Steps to Reproduce:

1. Write a function
2. Reference it somewhere
3. Mouse-Hover the function pops up a little box with informations

Just as described in https://code.visualstudio.com/docs/editor/editingevolved#_hover

Is there a way to disable it or at least set a delay?
I find myself in many situations where this just blocks my view.

[alexdima]

Unofficial (hence the squiggle you'll get), but here goes: "editor.hover": false

[misantronic]

Works quite well, thank you!

Its not that the hover-informations are bad, they just pop up everywhere :)
I would suggest to add a delay-option to keep the popup-rate low.

[alexdima]

It isn't user configurable, the delays is hard-coded to 300ms.

https://github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/hover/browser/hoverOperation.ts#L51

[WoodyWoodsta]

Incredible. I was just looking for this. The HTML and CSS hovers are way too verbose. I've been working with CSS for a while, I know what background does 😄

What would be better is if the popups could be triggered by some other, more intentional means, such as a keyboard shortcut. I'd hazard a guess that 95% of the time, the user wants information provided by the popup after actively deciding to find it. The hover action does not convey this degree of intention.

[alexdima]

At least on linux it is ctrl+k ctrl+i. Look for F1 > Show Hover

[WoodyWoodsta]

Brilliant 👍 Thank you.

[misantronic]

I get an error-message when doing so:
Cannot read property 'startShowingAt' of undefined

[WoodyWoodsta]

@misantronic Confirmed. Reloading the window does not resolve the issue.

[alexdima]

@misantronic @WoodyWoodsta ctrl+k ctrl+i works for me:

I position the cursor at the position I'm interested in and press ctrl+k crtl+i on windows:

Perhaps there's something more to it? (to get Cannot read property 'startShowingAt' of undefined ?

[WoodyWoodsta]

After looking around, it appears that the keybind works after setting editor.hover to false but only up until you reload the window. After reloading the window, the error shows. Setting editor.hover back to true only reflects when reloading the window again.

[WoodyWoodsta]

In my opinion, editor hovers could benefit from having more configuration. For example, hovers on linter errors are incredibly helpful (required, in fact, unless you want to keep opening the errors pane), but html tag info: not so much. Typescript-like info in a normal Javascript file is also a question mark in my mind. It is unfortunate that it is an all-or-nothing choice (and an unofficial one too). I am unsure of the mechanism behind hovers, but if this is something worth discussing further, then should a new issue be opened?

[misantronic]

@alexandrudima I am on mac and supossed to press ctrl + J. Whenever I do set the error-message pops up. Might be a mac issue?

@WoodyWoodsta I totally agree on that.
I use flow a lot and hovering is really helpful in those cases. but most of the time - I dont need the popups.

[DarrylD]

I use flow a lot and hovering is really helpful in those cases. but most of the time - I dont need the popups.

I'm in the same boat, any solution to this? I also get Cannot read property 'startShowingAt' of undefined

[romines]

See #32786

[amackintosh]

This is super annoying. "editor.hover": false, does work and requires a restart of VS Code, but it also disables ES Lint tooltips. I can't stand it and I can't live without it :(

[alexdima]

@amackintosh Problems can also be viewed in the problems panel (View > Problems) or in the editor via F8/Shift-F8

[amackintosh]

Thanks, but that is not efficient. I want every tool tip except this one:

The fastest possible solution would be to increase the hover time to like 500-1000ms, because it comes up pretty much instantly and prevents selecting text above the hover-triggering-text the mouse passes through.

I would like to see either of the following:

1. "editor-typescript-tooltips": false (only affects those tooltips of the type shown in the above screenshot)
2. user-definable "editor-hover-wait-time": "1000ms"

The best solution would be to make user-definable hover settings available and for each tooltip type.

Here is another screenshot to illustrate:

[alexdima]

@amackintosh The last screenshot is of parameter hints. editor.parameterHints: false. As for the type information hover, perhaps @mjbvz can transmit or capture the feedback to the TS team that the type information becomes useless in JavaScript when the type requires more than 100 chars to convey (i.e. is very complex or "not-nameable").

[mjbvz]

Yes we have a few issues tracking improving display of complex types:

• Quick Info needs to have its size capped TypeScript#1510
• [Suggestion] Display the name of type alias in quick-info consistently TypeScript#13095
• Use function type shorthands when displaying signature help TypeScript#8134