predragnikolic

For me the most logical choices is `c)` than `a)`. `b)` doesn't make much sens if options `a` or `c` are considered.

> From the code (for session in sessions:) I think you have implemented b) and not a) sessions refers to sessions running in the view (not sessions in the window)....

Here are the branches for each option: :) a) that inlay hints for one session in one window are hidden. -> this branch b) that inlay hints for all sessions...

Ok, I did some further experimentation. I introduced a new argument for the toggle command: ``` { "command": "lsp_toggle_inlay_hints", "args": { "args": { "toggle": "current_view" // values: "current_view", "current_window", "all_windows"...

My goal is to not add a lot of code for this feature and to avoid adding new settings as I'm not sure if I will cover all possible use-cases...

> it is difficult to remove it later in case we decide that it would be useful to have this toggle functionality also for other features I would not rush...

Made some adjustments to this branch to make this PR mergeable And also made it easy to switch to #2033 with [ead75b7](https://github.com/sublimelsp/LSP/pull/2023/commits/ead75b738136d6ccd76c62c81735b2cda96e2605) If you think that it is better to...

For servers that implement this, it will probably noticeably reduce the payload size send to the clients.

Something like this? ``` :: --> LSP-pylsp initialize (1 | 12:18:01): {'initializationOptions': {}, 'capabilities': {'general': {'markdown': {'version': '3.2.2', 'parser': 'Python-Markdown'}, 'regularExpressions': {'engine': 'ECMAScript'}}, 'window': {'showDocument': {'support': True}, 'showMessage': {'messageActionItem': {'additionalPropertiesSupport':...

What language server is this?