it puts all hover-on-type events into the inlay hints. this has some rendering bugs but they're all git related so just disable that feature or work around it.
reality is the battlefield
- she/they (pl)
- breadthcharge.net/
the first line goes in Cohost embeds
🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮
I speak to the universe and it speaks back, in it's own way.
mastodon
email: contact at breadthcharge dot net
I live on the northeast coast of the US.
'non-functional programmer'. 'far left'.
conceptual midwife.
https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut
If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.
You must log in to comment.
in reply to @NireBryce's post:
i cannot believe that the hover usability bug has existed for so long that someone had to build a workaround for it
it makes editing CSS files incredibly infuriating
judging by complaints about it, iirc it's been there since 2018. its so funny. the only people who thought this was a good idea must have been code reviewers
i have not found a good way to disable it or limit it without breaking other things
so bizarre, so much of VS Code is actually pretty good and the UI is leagues better than Atom was and most other GUI code editors, but just this one hill they want to die on i guess
Also:
- you can trigger the "hover" thingy by hand with (at least with VSCode's default keybindings) CMD+K and then CMD+I
- there's an extension that shows the doc of the currently hovered element in the sidebar/a panel https://marketplace.visualstudio.com/items?itemName=bierner.docs-view
recently on windows that binding breaks a lot. you can use it to disable the hoverbox on type, but it comes back if you hover over anything with the mouse
but yeah