I just did a distribution update on OpenSUSE and ended up with KWrite 22.12.0.
After doing nothing more than typing `kwrite` on the command line I am faced with the choice of reporting these two bugs:
1. "Intro" screen is completely unnecessary and breaks my workflow. If there is a program that doesn't need a welcome sort of UI, that is KWrite. Just open and start typing.
2. The menu hamburger appears twice. Once on the window decoration, as it's supposed to with my KDE settings, and again in the application itself. That is dumb.
But at the end of the day, this and other bugs such as what is reported under bug 458621 (and likely others) boils down to one thing:
**KWrite was fine as it was. It did not need any changes to the user interface. It didn't need tabs. It didn't need an unwelcome (sic) page. God knows what else has crept in that didn't need to be there.**
I appreciate that someone invested his time on these changes, no doubt with the best of intentions, and I am grateful for that; the intention was certainly noble. But the easiest way out is to go back to square zero (version 22.04.3 in this case) and unless something *is* broken, please leave it be. Thanks.
You can add to the above:
3. Toolbars shown configuration is not remembered from one window to the next.
Once again, reverting to 22.04.3 fixes this and the other problems.
KWrite is too important a part of KDE to mess around with it so casually.
That will not happen.
But bugs will be naturally fixed.
The welcome page can be disabled with one click for ever.
The hamburger button works as intended and can be removed in the config, too.
If e.g. toolbar config is broken, open an own bug.
(In reply to Christoph Cullmann from comment #2)
> But bugs will be naturally fixed.
Including the extra complexity added to the code base for no apparent reason? Think of the next maintainer.
Also, traceability leaves a bit to be desired. I cannot find where these changes stemmed from. I found some of the merge requests, but those just seem to pop out of the blue.
There should be a corresponding bug report in the tracker and a link to it in the merge request / commit message. Likewise, bug reports that originate in a mailing list should link to the archive or at least copy the relevant parts. Otherwise there is no context for people to understand what's going on.