vis-lspc/README.md, branch v0.1.8 language server protocol client for the vis editor fix typo 2023-01-14T16:41:08+00:00 Florian Fischer florian.fischer@muhq.space 2023-01-14T16:41:08+00:00 b39ef7bba0cd881763307c85c9f2e4365336da18 






link to the shipped language server configurations
2023-01-14T16:27:23+00:00

Florian Fischer
florian.fischer@muhq.space

2023-01-14T16:27:23+00:00

24cf81f1c25a93fe3300cc103651938f5867f7cd












support configuration and initializationOptions per language server
2023-01-14T16:22:46+00:00

Florian Fischer
florian.fischer@muhq.space

2023-01-14T15:21:22+00:00

2719e586fcbbe63d6652605d2e3aeee22274e511

Send language server settings after initialization via a
workspace/didChangeConfiguration notification.

Implement a workspace/configuration handler using the values stored
in the language server settings.

Send the init_options as initializationOptions in the initialize
parameters.





Send language server settings after initialization via a
workspace/didChangeConfiguration notification.

Implement a workspace/configuration handler using the values stored
in the language server settings.

Send the init_options as initializationOptions in the initialize
parameters.







move server configurations into a seperate file
2022-08-01T15:47:59+00:00

Florian Fischer
florian.fischer@muhq.space

2022-08-01T15:45:29+00:00

8e90351411d0312493c56d59058785d11b282145












send clientCapabilities
2022-02-20T13:15:57+00:00

Florian Fischer
florian.fischer@muhq.space

2022-02-20T13:13:04+00:00

47b7b1e47bb10183f5b4ee84d90b4e3eefabe75c

Be nicer to the language servers by providing our capabilities so
maybe we get more deterministic results.

We do not support dynamicRegistration, markdown or workDoneProgress.





Be nicer to the language servers by providing our capabilities so
maybe we get more deterministic results.

We do not support dynamicRegistration, markdown or workDoneProgress.







mention that our bundled json impl does not support utf-8
2022-02-20T13:09:54+00:00

Florian Fischer
florian.fischer@muhq.space

2022-02-20T13:09:54+00:00

e277fe0994cf32359f701e1875e231e39183f316












README: update configured language servers
2021-12-28T12:52:52+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-28T12:52:52+00:00

d4e6d51931290db7434d49ae6b913e4850b8c63d












try multiple json implementations
2021-12-27T19:46:39+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-27T19:46:39+00:00

655dafe59e35a2bc7bd0785c342c47e3ea860c70

We try 'json', 'cjson' and 'dkjson' in that order before using our
bundled fallback implementation.





We try 'json', 'cjson' and 'dkjson' in that order before using our
bundled fallback implementation.







Mention easy installation of vis-lspc with GuixRUs
2021-12-24T11:04:40+00:00

jgart
47760695+jgarte@users.noreply.github.com

2021-12-24T11:04:40+00:00

5408aa2320d2c7744d8064d4619d9ed3fe996d53












improve default logging
2021-12-13T12:24:01+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-13T12:24:01+00:00

14b2a777085b60f2b0fba4cfc8407d9228758f44

I use to have logging enabled to be able to debug weird vis-lspc
behavior right away. But I got annoyed by vis-lspc cluttering all my
directories with vis-lspc.log files.
So vis-lspc will no write its log files to
$XDG_DATA_HOME/vis-lspc/<iso-date>-<cwd-basename>.log if
lspc.log_file is not set by the user.

This patch also introduces a helper to run a program and capture
its output.





I use to have logging enabled to be able to debug weird vis-lspc
behavior right away. But I got annoyed by vis-lspc cluttering all my
directories with vis-lspc.log files.
So vis-lspc will no write its log files to
$XDG_DATA_HOME/vis-lspc/<iso-date>-<cwd-basename>.log if
lspc.log_file is not set by the user.

This patch also introduces a helper to run a program and capture
its output.