vis-lspc/lspc.lua, branch detect-root language server protocol client for the vis editor make universal root detection opt-in 2025-01-11T14:11:16+00:00 Florian Fischer florian.fischer@muhq.space 2025-01-11T14:11:16+00:00 29afc301ea05bc907444b698c91b141c26167baa 






move the fzf detection snippet into lspc.lua
2024-08-27T20:16:15+00:00

Florian Fischer
florian.fischer@muhq.space

2024-08-27T20:13:07+00:00

87edef4dff8ab931a9ec85de9a11cbd4cc7d6247

It changes a default setting keep it in the file where the default
settings are defined.





It changes a default setting keep it in the file where the default
settings are defined.







make the message handling functions methods of the lspc object
2024-08-27T20:16:15+00:00

Florian Fischer
florian.fischer@muhq.space

2024-08-27T20:08:31+00:00

1bd1416c89f92f637ca5e22c94b3479f8d32f2d7

Move the logging code into its own module and export the default logger.
Other modules can use the logger exported in the lspc table.





Move the logging code into its own module and export the default logger.
Other modules can use the logger exported in the lspc table.







use vis' event system instead of custom language server hooks
2024-04-30T20:32:02+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-30T20:32:02+00:00

05feb47b380d38d20af824ede7b43d0e2d1f9ecb












lspc, init: emit LS_INITIALIZED and implicitly call lspc_open on server init
2024-04-30T20:18:24+00:00

git-bruh
prathamIN@proton.me

2024-04-06T20:27:40+00:00

e505535d40d44a0bda341b37a5611663ef9815fe












use a global mapping of open files
2024-04-30T19:39:15+00:00

Florian Fischer
florian.fischer@muhq.space

2023-11-16T15:10:26+00:00

65b57fade82e0ad6ce3bdb8f8fa03e807eb29b16

This allows us to support opening a single file in multiple
language server instances.
This can be useful when combining for example a latex and a language
tool language server.





This allows us to support opening a single file in multiple
language server instances.
This can be useful when combining for example a latex and a language
tool language server.







support highlighting line numbers using vis:style_pos
2024-04-25T18:26:05+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-25T15:51:02+00:00

53c6d728d0f39e361a1922f77f45786616f69f1c

Replace the hacky style_lineno code with the new vis:style_pos
API probably included in upcoming vis v0.9.





Replace the hacky style_lineno code with the new vis:style_pos
API probably included in upcoming vis v0.9.







make the way messages are presented configurable
2024-04-15T16:04:10+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-12T09:10:17+00:00

0e71c4a1e7aabcad269ffb1cdd3f53da6ef31df4

The two options are either using vis:message (the default) which will
keep all messages in the vis message buffer and include a header line to
distinguish the different messages.

The second option is using open and presenting messages in a separate
window supporting syntax highlighting.





The two options are either using vis:message (the default) which will
keep all messages in the vis message buffer and include a header line to
distinguish the different messages.

The second option is using open and presenting messages in a separate
window supporting syntax highlighting.







_show_markdown_message: helper for markdown info
2024-04-12T08:11:08+00:00

git-bruh
prathamIN@proton.me

2024-04-01T18:03:07+00:00

85ace3c4355d7bb9f981b9d24a84c790347575c5












enable diagnostic highlighting by default
2024-04-11T15:02:54+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-11T15:02:54+00:00

1a34f650a6b7e1fef84c4bddd034893fe9bb5ff3

This is inline with our README.md claiming 'line' is the default
value for highlight_diagnostics.





This is inline with our README.md claiming 'line' is the default
value for highlight_diagnostics.