vis-lspc/lspc.lua, branch show-message language server protocol client for the vis editor make the way messages are presented configurable 2024-04-12T09:10:17+00:00 Florian Fischer florian.fischer@muhq.space 2024-04-12T09:10:17+00:00 05c733a806993b6cd3601587d4655811c1c771c0 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.







use less instructive default styles for highlighting diagnostic
2024-04-11T15:00:37+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-11T15:00:37+00:00

30c94b345f00caff698dc6976e17e829560fdb17












chnage default diagnostic styles and mention them in the README
2024-04-11T08:44:10+00:00

Florian Fischer
florian.fischer@muhq.space

2024-04-11T08:44:10+00:00

6badd1c874fd72bb7127bf72e4d006a3bd5c18a8












lspc, init: add different diagnostic styles for each type
2024-04-11T08:40:08+00:00

git-bruh
prathamIN@proton.me

2024-04-06T19:46:43+00:00

435559d6ff94ba861c67a486736af5c506348326












Merge branch 'apply-workspaceEdit-remember-cursor' into 'main'
2024-04-08T17:35:25+00:00

Florian Fischer
gitlab@muhq.space

2024-04-08T17:35:25+00:00

d36c417bc662a720a0bfdd60cbc8c1dc6c915041

restore the primary cursor position after a workspaceEdit

See merge request muhq/vis-lspc!47




restore the primary cursor position after a workspaceEdit

See merge request muhq/vis-lspc!47






lspc: explicitly specify publishDiagnostics in client_capabilities
2024-04-08T17:19:39+00:00

git-bruh
prathamIN@proton.me

2024-04-07T19:12:28+00:00

ac7bdc1f1a84d9e7bbd28f091700993362b72525












restore the primary cursor position after a workspaceEdit
2024-03-22T09:23:28+00:00

Florian Fischer
florian.fischer@muhq.space

2024-03-22T09:21:43+00:00

e44ec3fa609fa7701de369939674a1ea46743ea8












increase thedefault style id
2023-10-25T14:03:33+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-25T14:03:33+00:00

754dad10d3a8434d0c23f919b592d76aa32ace46

Using the new latex lexer from the upcoming vis release I noticed
that vis-lspc default style id 43 overrides the environment style
from the lexer.

To prevent id clashing use the highest allowed id for lexer styles,
which is 64 according to the enum defined in vis/ui.h.





Using the new latex lexer from the upcoming vis release I noticed
that vis-lspc default style id 43 overrides the environment style
from the lexer.

To prevent id clashing use the highest allowed id for lexer styles,
which is 64 according to the enum defined in vis/ui.h.