kde

The new LSP client by Mark Nauwelaerts made nice progress since the LSP client restart post last week. Reminder: The plugin is not compiled per default, you can turn it on via: cmake -DCMAKE_INSTALL_PREFIX=“your prefix” -DENABLE_LSPCLIENT=ON “kate src dir” The code can still be found kate.git master, see lspclient in the addons directory. What is new? Diagnostics support: A tab in the LSP client toolview will show the diagnistics, grouped by file with links to jump to the locations....

Since my last post about the LSP client progress in May I didn’t work on that project at all I think. But the good news is, somebody else did scratch that itch on his own ;=) We have now a prototype plugin in kate.git master, see lspclient in the addons directory. It is not compiled per default, you can turn it on via: cmake -DCMAKE_INSTALL_PREFIX=“your prefix” -DENABLE_LSPCLIENT=ON “kate src dir”...

While browsing the ISO C++ homepage I stumbled over the results PDF of the Second Annual C++ Foundation Developer Survey “Lite”. I was astonished that Kate made it into the “Which development environments (IDEs) or editors do you use for C++ development?” results. ;=) Seems not only I use it as my normal editor for working on C++ code. And heads up, KDevelop is there, too! This is actually the second survey, I missed to notice the first one last year....

Two days ago I mentioned here that the bug report count of KTextEditor and Kate has risen to some not that manageable amount. For developers that report a bugs or wish, the best way to really get it solved is to scratch your own itch and provide some patch. I know this is not feasible for all bug reporters, as not all are developers nor will even the developers all have either time nor perhaps the right skill set to tackle the issue on their own....

The bug report count of KTextEditor (implementing the editing part used in Kate/KWrite/KDevelop/Kile/…) and Kate itself reached again some value over 200. If you have time and need an itch to scratch, any help to tackle the currently open bugs would be highly appreciated. The full list can be found with this bugs.kde.org query. Easy things anybody with a bit time could do would be: check if the bug still is there with current master builds, if not, close it it check if it is the duplicate of a similar still open bug, if yes, mark it as duplicate Beside that, patches for any of the existing issues are very welcome....