kate lsp client plugin

Mark Nauwelaerts mark.nauwelaerts at gmail.com
Tue Jul 16 08:27:04 BST 2019

On 16/07/19 09:13, Christoph Cullmann wrote:
> Hi,
>> If there is need to have access to document variables, we can
>> introduce that again,
>> thought I am not sure this is the solution to go, given I would actually prefer
>> something that needs to annotation/config that is Kate specific in the sources.
>> Perhaps some clever heuristics would be good enough, but that is something
>> for the time after all other polishing is done.
>> For the diagnostics output in the tab it would be very nice if always
>> the current document
>> would be "activated" there, but otherwise this already works ok for
>> the first version!
>> :=) At least some of my colleagues were impressed about the stuff that
>> already works
>> and that you need to configure nothing for this at all.
> the 19.08 release branch got created.
> I would like to enable the plugin for compilation in master
> to have it installed per default for post 19.08 development
> setups.
> Would that be ok?
> Greetings
> Christoph
That's fine by me, assuming that does not prohibit making some (backwards 
incompatible) changes to behavior and/or configuration as/when things may evolve 
in such a way (but presumably ok for only on master and not released yet) ...


More information about the KWrite-Devel mailing list