Skip to content

KTextEditor - Small Things Matter - Continued

Sunday, 13 December 2020 | Christoph Cullmann

Noise inside the terminal?

I more or less always start my Kate session inside a terminal, to let the project plugin auto-load the right one for the current working directory.

What I ignored for a long time is the noise this produces inside the terminal.

If you launch Kate or KWrite, you will often get stuff like (even for release builds):

kf.sonnet.core: Unable to find any suggestion for "dummy to trigger identify"
kf.kio.core: We got some errors while running testparm "Weak crypto is allowed\nERROR: Invalid idmap range for domain *!"

The first one stems from the language identification we trigger at startup to fix input lag for lazy loading of Sonnet things.

The second one stems from “testparm” execution to discover Samba shares. If you have no Samba configured at all, this message will differ.

Is this really wanted?

As nice this might be for debugging, I think for the normal user this is pointless.

No valid suggestion in Sonnet is just a valid API result, no need to inform the user on the terminal/log.

Same for Samba stuff: In many cases the user not even configured that at all or isn’t able to modify the potential “bad” Samba configuration. In my case these settings are even intentional the way they are out of compatibility constraints in the local network.

There is really no point in filling either the terminal window or the session log with such stuff.

After a long time ignoring this, at least this noise is now removed:

Same for some other kbuildsyscoca noise that sometimes happens, if you have auto-generated dummy files around:

Kate & KWrite (and stuff like Dolphin) now start up without any ugly noise (with current Frameworks from Git on a Manjaro system)!

Can more be done?

With a disabled/non-functional Baloo I still get here for Dolphin or Kate with the file system browser plugin:

kf.kio.core: "Could not enter folder tags:/."

I yet need to find a way to remove this the “proper” way. If somebody has some trivial fix for this, that would be welcome!

Help welcome!

As you see, it is trivial to avoid such messages in the most cases. If you are annoyed with such things, please provide patches on to improve the situation.