thblt · 2022-11-04 19:42
There's some nice irony in auto-enabling features "to improve discoverability" only to end up having to write an article because users can't discover how to *disable* them :)
PhantomSeahorse · 2022-11-04 20:41
How is that an irony?
hey_parkerj · 2022-11-05 01:55
Genuine question - what could that do to improve discoverability? Obviously every var starts with lsp- but should they all start with lsp-enable? (Just and example pulled from one of the vars). Is the default expectation for lsp packages that people read the source or scan the vars and functions to determine what to enable/disable?
thblt · 2022-11-05 10:40
Out of my head, what about minor modes ? You could start them from a prepopulated lsp-mode-hook, they have modeline indicators so you can easily notice and disable them..
yyoncho · 2022-11-05 12:38
Indeed. It is "pick your poison" - either having everything off and most people will never discover the feature or having everything on and having some people complaining...
celeritasCelery · 2022-11-05 14:34
This is great! Gives a name to every feature on the screen. One thing I don’t see here is how to disable inlay hints. Maybe because those options are LSP server specific?
sibip · 2022-11-05 15:38
Yeah, I believe so. Example for rust-analyzer: https://emacs-lsp.github.io/lsp-mode/manual-language-docs/lsp-rust-analyzer/#inlay-hints
celeritasCelery · 2022-11-05 17:57
Is rust-analyzer the only lsp server with inlay hints?
Shivalicious · 2022-11-08 11:44
No, typescript-language-server has them too. (I’m not familiar with any others.)