vis-lspc/init.lua, branch v0.1.4 language server protocol client for the vis editor bump version to 0.1.4 2021-12-13T12:33:43+00:00 Florian Fischer florian.fischer@muhq.space 2021-12-13T12:33:43+00:00 c60f7f44aad12382cb55057339277d7f3db8e9a8 






use capture_cmd where possible
2021-12-13T12:27:30+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-13T12:27:30+00:00

b69830edda38ad57457eb0e0c55e63326930e6db












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.







add menu-/ confirm-cmd options
2021-12-08T12:34:47+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-08T12:34:47+00:00

dc690693793a06cb7f84f93703f00ff727eb54c2












fix ff92a0f1fca0f0db5b00022fc2ac41579ac5ab24
2021-12-06T09:56:29+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-06T09:53:18+00:00

92993f2b2146273c9f421d1e8410ee65f8f33105

Don't use a global variable.





Don't use a global variable.







handle string or MarkContent documentation in SignatureInformation
2021-12-06T09:33:32+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-06T09:33:32+00:00

ff92a0f1fca0f0db5b00022fc2ac41579ac5ab24












do not try to handle error responses
2021-11-22T09:46:18+00:00

Florian Fischer
florian.fischer@muhq.space

2021-11-22T09:46:18+00:00

b08f3bfbb0428aba83968d3339e12c7e29d7997a












fix crash in error reporting
2021-11-21T12:26:25+00:00

Florian Fischer
florian.fischer@muhq.space

2021-11-21T12:26:25+00:00

37ef27177133eca24254e278d37497b5842f18fd

We crashed because a forgotten concatenation operator





We crashed because a forgotten concatenation operator







do not use lspc.log before lspc is initialized
2021-08-29T10:14:12+00:00

Florian Fischer
florian.fischer@muhq.space

2021-08-29T10:09:29+00:00

6549f12af82dcf3fc204a0e2e5caf60acc7af477












bump version to 0.1.3
2021-08-16T12:14:41+00:00

Florian Fischer
florian.fischer@muhq.space

2021-08-16T12:14:41+00:00

86ec0a64964a9b8afd73d65b5156648b0d9d564e