vis-lspc/init.lua, branch apply-workspaceEdit-remember-cursor language server protocol client for the vis editor 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 






Fix lscp.open_file not actually adding to history
2023-11-21T12:58:37+00:00

Michiel van den Heuvel
michielvdnheuvel@gmail.com

2023-11-21T12:58:37+00:00

17e40a5be84b51fa004a985c004d3ff34e477662












fix wandering empty diagnostic highlights
2023-10-12T18:14:57+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-12T18:14:57+00:00

ecd67870e578c061b06ecc4072477da5e9ea9f52

The last commit introduces support for highlighting empty selections
by properly calculating their vis ranges.
However File:content does return an empty string for empty ranges
and we can not check whether the diagnostic still applies to the same
position.

This is fixed by faking a one character range when receiving an
empty one.
Doing so we get a valid one-character content we can compare and
still have proper highlighting because we unconditionally decrement
the range end in highlight_diagnostics.

Fixes: 7099e56062861fc8dbb143e78447cce6bf886a97





The last commit introduces support for highlighting empty selections
by properly calculating their vis ranges.
However File:content does return an empty string for empty ranges
and we can not check whether the diagnostic still applies to the same
position.

This is fixed by faking a one character range when receiving an
empty one.
Doing so we get a valid one-character content we can compare and
still have proper highlighting because we unconditionally decrement
the range end in highlight_diagnostics.

Fixes: 7099e56062861fc8dbb143e78447cce6bf886a97







fix diagnostic highlighting and message
2023-10-12T16:52:19+00:00

Thim Cederlund
thim@cederlund.de

2023-10-11T15:28:59+00:00

7099e56062861fc8dbb143e78447cce6bf886a97

Some language servers report diagnostics with empty ranges, start and
end are at the same line and character, which currently results in
no highlighting at all.

Since the end of a LSP range is exclusive we always subtract 1 from
it which results in invalid ranges when the server has sent an empty one.
Introduce a check to fix this special case.

`textDocument/publishDiagnostics` doesn't always have a `code` field,
resulting in `diagnostic.code` being nil and so it is replaced with
`diagnostic` in those cases.





Some language servers report diagnostics with empty ranges, start and
end are at the same line and character, which currently results in
no highlighting at all.

Since the end of a LSP range is exclusive we always subtract 1 from
it which results in invalid ranges when the server has sent an empty one.
Introduce a check to fix this special case.

`textDocument/publishDiagnostics` doesn't always have a `code` field,
resulting in `diagnostic.code` being nil and so it is replaced with
`diagnostic` in those cases.







allow to specify the syntax to use for the diagnostics commands
2023-10-12T16:50:28+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-08T08:38:55+00:00

c91a9c94b1408a308a33acbe56e8eb9bcf86d197












report if no diagnostics are available
2023-10-12T16:50:20+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-08T08:18:27+00:00

1d9b9603bb98a0cd0fc8240cbe0a7989bf785db0

Since the diagnostics table is created when we open the file
it will always be ~= nil.





Since the diagnostics table is created when we open the file
it will always be ~= nil.







store diagnostics received for files not in the current window
2023-10-12T16:50:09+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-08T08:02:23+00:00

067ec7dd2d5006af72aa73a4fada5380da5c0126












implement cycling between available diagnostics
2023-10-07T08:35:01+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-07T08:35:01+00:00

cb0153aa0f10259037dc7cdb69d75f64909657e1

This is implemented by the two new commands:
  * lspc-next-diagnostics - jump to the next available diagnostic
  * lspc-prev-diagnostics - jump to the previous available diagnostic





This is implemented by the two new commands:
  * lspc-next-diagnostics - jump to the next available diagnostic
  * lspc-prev-diagnostics - jump to the previous available diagnostic







fix diagnostics line highlighting
2023-10-06T11:28:08+00:00

Florian Fischer
florian.fischer@muhq.space

2023-10-06T11:28:08+00:00

59d46b01ce5985d51c7b761b948060aa8b11d35b

Range highlighting used the vis_range and line highlighting the LSP
range. Do not touch old code you no longer understand because you think
you are apparently smarter than your past self!

Fixes: efd5262f2c45d3289e482b1091d3c1d44cf67a42





Range highlighting used the vis_range and line highlighting the LSP
range. Do not touch old code you no longer understand because you think
you are apparently smarter than your past self!

Fixes: efd5262f2c45d3289e482b1091d3c1d44cf67a42







use vis default formatting options
2023-10-06T11:16:19+00:00

Florian Fischer
florian.fischer@muhq.space

2023-08-25T09:57:03+00:00

15fbc713017dc6db6bdca7b16a2b9a3f4e201867

Since vis 0.9 the options are exposed via the vis.options table.





Since vis 0.9 the options are exposed via the vis.options table.