Tags: opntr/vim-lsc
Tags
Fix diagnostic truncatign for multi-byte chars In some cases where a mult-byte character was at the truncation point it could get broken and end with with things like `<e2><86>` in the output. Use `strtrans` to get the string as it would be printed, then `strchars` and `strdisplaywidth` to truncate to handle both multi-byte and wide characters. Add changelog for duplicate word completion and prepare to tag for release.
Add LSClientFindCodeActions This is very conservative for now. Edits must be enabled with a global variable since they are risky, and they only will apply in the current buffer. - Allow choosing a code action following a call to `findCodeActions` and then call `workspace/executeCommand` - Add dispatching for `workspace/applyEdit` to a function which selects the changed range and replaces the text. - Take a server argument to dispatch so that requests can send back a resonse. - Add mapping to `ga`. The default behavior is to print the ascii code of the character under the cursor. - Update the client capabilities to indicate applyEdit if it is enabled. Future Work: - Add support for edits in other buffers. - Allow a visual mode call which sends a range rather than a single character under the cursor.
PreviousNext