Kate | Get an Edge in Editing

At the moment the Document Preview plugin that e.g. allows to preview Markdown or other documents layout-ed via embedding a matching KPart is no longer maintained. You can find more information about why the plugin got abandoned in this phabricator ticket. If you want to step up and keep that plugin alive and kicking, now is your chance! Even if you don’t want to maintain it, you can help out with taking care of existing bugs for this plugin. [Read More]

The default configuration for the Kate LSP client does now support more stuff than just C/C++ and Python out of the box. In addition to the recently added Rust support we now support Go and LaTeX/BibTeX, too. Configuration The default supported server are configured via some JSON settings file we embed in our plugin resources. Currently this looks like: { "servers": { "bibtex": { "use": "latex" }, "c": { "command": ["clangd", "-log=error", "--background-index"], "commandDebug": ["clangd", "-log=verbose", "--background-index"], "url": "https://clang. [Read More]

Initial support for the rls Rust LSP server has landed in kate.git master. The matching rls issue about this can be found here. Given I am no Rust expert, I can only verify that at least some operations seem to work for me if the Rust toolchain is setup correctly ;=) The current experience isn’t that nice as with clangd, for example I get no symbols outline here. What is possible with clangd can be seen in one of my previous posts, video included. [Read More]

Like my personal homepage cullmann.io, I ported the kate-editor.org website to the Hugo framework. The new website uses zero cookies (yes, no stupid cookie question) and no kind of analytic software. It should be self-contained, too. No external resources that will leak your data to e.g. Google are requested. But more important: unlike before, the website content will be fully hosted in a git repository on KDE infrastructure. The current intermediate location is on invent. [Read More]

After my series of LSP client posts, I got the question: What does this actually do? And why should I like this or help with it? For the basic question: What the heck is the Language Server Protocol (LSP), I think my first post can help. Or, for more details, just head over to the official what/why/… page. But easier than to describe why it is nice, I can just show the stuff in action. [Read More]

The new LSP client by Mark Nauwelaerts keeps making nice progress. It will not be shipped with the KDE Applications 19.08 release, but in master it is now compiled & installed per default. You only need to activate it on the plugin configuration page in Kate’s settings dialog to be able to use it. For details how to build Kate master with it’s plugins, please take a look at this guide. [Read More]

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. [Read More]

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” [Read More]

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. [Read More]

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. [Read More]