vis-lspc/init.lua, branch lspc-wo-vis-syntax language server protocol client for the vis editor use win.lsp_syntax instead of win.syntax 2022-01-21T09:54:37+00:00 Florian Fischer florian.fischer@muhq.space 2022-01-21T09:54:37+00:00 b4cef48a87566c9eb9791c3d5429c0293cffc713 






reformat ls_map tables as a table literal
2021-12-28T12:33:19+00:00

Matěj Cepl
mcepl@cepl.eu

2021-12-28T01:12:02+00:00

5bcf29a8ee3c0f78b132a2f8acddf2c71206dbbd












add Lua LSP server configuration
2021-12-28T12:33:01+00:00

Matěj Cepl
mcepl@cepl.eu

2021-12-28T01:03:20+00:00

03d7ebe23246e9f70fd11f21dae0ee259b678694












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.







actually use python-lsp-server binary
2021-12-27T19:09:01+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-27T19:09:01+00:00

4d8420d30d47d738221845bb95759e9420cdb788












change default python language server to pylsp
2021-12-27T18:33:49+00:00

Florian Fischer
florian.fischer@muhq.space

2021-12-27T18:32:57+00:00

0fb192f2e78a61718832e07c98b72c00d137ea57












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