That seems a bit contrived to me. Okay, that particular place is pretty deeply nested, but it's clearly a regular menu tucked away in there, with a option to show the menu bar. If you turn that on, then those options are half as deep. Or if you don't need to adjust those options, you don't go that deep.

The sibling comment, meanwhile, is complaining about extra space devoted to explicit controls for all of the extra options. Well, you can't have it both ways. If you want to have a lot of features and options, you have to either devote some space in the main UI to them, or have a lot of deeply nested menus like that.

Or I guess you could do a config file somewhere, but IMO that's even worse. If we're going to complain about bad UIs, isn't it even worse than some deeply nested menus to need to open a separate file somewhere else with a separate program and learn whatever config file syntax they happen to use.

While I prefer deeply nested menus (and I acknowledge I'm a weirdo at that) there's plasma-manager if you happen to use Nix and home-manager. I don't know if it will help in that specific case but if you'd rather have the config in a well documented file this could generally help.

https://github.com/nix-community/plasma-manager

Nothing wrong with nested menus. The problem is that plasma has a classic File menu inside of a hamburger menu hidden under a "More" button with a whole set of duplicated options that can be found in other parts of the interface. It's nuts.

I'd rather have all that mess removed and settings 1% of the user base "needs" moved to a config file. I don't want to add an another layer of complexity with external configuration tools.

Uh, dolphin could really use a rewrite IMO, but first we'd need to agree of how it should look like :(