Happy news arrived on the kwrite-devel mailing list with this post before Easter 😉
Kate has won the advanced text editor comparison in the Linux Voice magazine – Issue 2, yeah 😉
Nice to see that our work on Kate is awarded.
About Linux Voice: Seems to be some pretty new magazine about Linux & Open Source (Issue 2 says it all) and they promise to give 50% of their profit back to the Free Software community, developers and events. Hope that works out, it is a nice goal.
P.S. And yeah, this is just one comparison and no, lets not start the “editors wars, … edition” in the comments, there are a lot of text editors to choose between and depending on your needs and preferences Kate might not be your favorite 😉
Kate comes with a build plugin, which supports running make, or ninja, or actually any arbitrary command directly from within Kate. This is obvisouly useful when using Kate as development editor, and this plugin has seen several improvements for the 4.13 release.
A small change, but for affected developers a major improvement, is that Kate can now parse warning and error messages from the Intel compilers, icpc and icc.
So for those of you using icpc, Kate can now automatically jump to the line of code which caused the error. Actually you don’t have to wait for 4.13 for this, it is already available since 4.12.3.
Beside that, there are improvements which benefit all users of the build plugin. Let’s start with a screenshot, which already shows one of the major changes.
Up to 4.12, it was possible to create multiple “targets”, and each of these targets could contain a “Build” command, a “Clean” command and a “Quick” command. As of 4.13, the build plugin is not limited anymore to these three commands. As can be seen in the screenshot, every “target set” can now contain an arbitrary number of actual targets.
They are listed in a table widget. To add a target, click the green “plus”-button in the lower right. This will append a target to the end of the list. It can be edited by simply double clicking it (or pressing F2 while keyboard focus is in the table).
To delete a target, click the “minus”-button right next to the “plus”
One of the targets can be marked as the “default” target. This will typically be the target which runs “make all”. Additionally one target can be marked as the “clean” target, this will typically be “make clean”. For these two special targets separate keyboard shortcuts can be assigned, so they are always quickly available.
A whole set of actions which can be bound to shortcuts can be seen here:
Now to the actually interesting part: building something.
There are multiple ways how to start building a target.
The default and the clean targets can be built directly using keyboard shortcuts, in the screenshot above I assigned F8 to the default target.
To build another than the default target, you can select the target you want in the table and then build it by clicking the blue “check”-button next to the “plus” and “minus” buttons.
For keyboard users, there is a quick-select dialog. It shows a list with the names of all targets, which can be filtered by typing part of the target name. That’s a really quick way to build any of the available targets. Here’s a screenshot:
Once building has started, the output is displayed in the log view.
As can be seen, there is only one output tab left, where the “level of detail” can be adjusted using a slider. While building, the plugin automatically switches to the log display.
Also new, there is now a simple status display, which tells you which target is currently being built or was built previously.
Next to it, there is yet another way to start a build, the “Build again” button. Once some target has been built, using this button the same target can be built again. Oh, and there is now also a button to cancel a build, in case you forgot the assigned keyboard shortcut.
When building has finished, the output tab automatically switches to a parsed output mode, which lists the warning – and error messages. By double clicking on one of them or using the keyboard shortcut of your choice, I assigned F9, you can jump directly to the line of code which caused the error.
All that together, should make the build plugin even more useful than before.
Have fun compiling !