![]() ![]() The 21.04 release uses a new fuzzy matching algorithm, providing the best results at the top, with less likely results located at the bottom. The Quick Open dialog used to use a wildcard filter for its top result, with direct matches to the search term being listed beneath it. The fuzzy matching is also a welcome improvement. Although minor, this change definitely is more eye-pleasing and helps improve the layout for those with larger screens. The new UI is the result of a move to a more consistent design throughout Kate. Now with the new 21.04 release, it is receiving a major overhaul, with things such as Fuzzy Matching and a new UI that aims to be more consistent with the Command Palette. Quick Open (With Fuzzy Matching)Ī longtime feature of Kate, Quick Open hasn’t been improved all that much over the past few years. Now with the integration into Kate, I can happily switch, without worrying about a huge disruption to my workflow. The Command Palette is possibly one of the most commonly used features in VS Code, and it has been one of the few things that have kept me using the aforementioned text editor. After waiting for years, this huge feature has finally been added to Kate. One of the key components of the VS Code workflow is the Command Palette. This is a a huge feature, and I suspect that it will be welcomed by developers everywhere. This is a huge improvement over the old way of using Kate’s built-in terminal to manage your repositories.Īdditionally, it opens up the ability to use git on the Windows version of Kate, which still doesn’t have the ability to access a command line (most likely due to the locked-down nature of it). Although it has been possible to load git repositories in Kate for a while now, the new integrated git support allows you to checkout and create branches, stash stuff, stage your files for commit or diff, and do the commit and push afterward, all without touching the terminal! One of the biggest features of this update is the integrated git support. Improved Language Server Protocol (LSP) support.Some of the features I will be looking at in this article include: ![]() Microsoft VS Code has had a similar style command palette for a long time, which Kate users (until now) had to leave out of their workflow. To the Visual Studio Code users out there, this may seem familiar. With this release comes a huge range of new features, such as a new HUD style command palette and improved search in files. To build the KF5 based Kate/KWrite you can follow the guide on KDE on macOS.KDE has revealed some details on the upcoming 21.04 release of their Kate text editor, or KDE Advanced Text Editor. To build the KF5 based Kate/KWrite you can follow the guide on KDE on Windows. If you have questions you can ask them on our mailing list and/or join #kate on .įor more information see Get Help. Contribute back!įeel free to create a merge request at .įor more information see Join Us. Other nifty stuff like project wide quick open, search & replace and correct build targets should be setup, too. Given the above setup, the LSP plugin (if you have clangd installed) should work out of the box. The second terminal is inside your source directory, perfect for e.g. run your ninja and ninja install commands and such. The first terminal is inside your build directory, here you can e.g. In the lower "Current Project" tool view you have per default two terminals. You will end up with a new Kate windows like shown below. If you like to have some GUI build integration, activate the build plugin, too. ![]() To have the best experience with this, ensure you have at least project & LSP plugin enabled. You can re-use this for development on any part of the KDE software stack.įor the remaining parts of this description we use Choose your Kate & KDE development directoryĬhoose yourself some path where all Kate & KDE development things should end up.īeside user local configuration files, nothing outside of this directory will be polluted. This eases contributions to all levels of the KDE software stack. Required KDE Frameworks will be compiled in addition to the Kate application parts. This avoids the need for administrator rights and allows always to fallback to use the global installed Kate if the currently build version is broken.Īs this tutorial will introduce a setup that allows to develop other parts of the KDE software stack, too, we will talk in the following about setting up a KDE development environment. This tutorial explains how to build Kate without touching your global installation.Īll stuff will happen inside an extra development directory. Right now, Kate's source code is located on the GitLab instance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |