[kmail2] [Bug 509043] Allow disabling "what's new"
Thomas Baag
bugzilla_noreply at kde.org
Thu Sep 4 20:58:39 BST 2025
https://bugs.kde.org/show_bug.cgi?id=509043
--- Comment #5 from Thomas Baag <bugs.kde.org at spam.b2ag.de> ---
> As you wrote it's on each computer, if you have 1 PC you just need to click once.
That's what I've guessed already. Again, I have four with KDE PIM stuff and six
in total. All of them sport a rolling release distro. Meaning features hash
could change more often than you'd expect. For the four PCs with KDE PIM on it
Kmail CANNOT write to kmail2rc. I hope you start to see the problem.
> for me it's the default.
> I don't think it's critical :)
If I do nothing about it, this banner will be displayed all of the time for me.
It will never go away because I have to actively do something to make it go
away. I need to find out the current hash value and put it into my static
kmail2rc, because, again, Kmail CANNOT write this file, it is static and on a
read-only mount. The visual annoyance is not critical enough to do those extra
steps every time. So it will be displayed all the time for me. You see?
> But for sure "what's new " is for informing user, otherwise I can remove all.
> So no I will not add more settings for it.
That's why I'd ask you to handle the case where it's missing from kmail2rc
differently. Currently you assume that the banner should be shown in a first
run scenario (or didn't think about this case at all). So it is shown not only
if a new feature is added, but also on the very first run of Kmail. Why not
change this behavior? Do you understand what I mean or should I attach a patch
as an example? It's not a setting. It's a different default for a missing
config value.
> For me user need/want to be informed.
I've no issue with that. My issue is with the banner being there all of the
time for me informing me of nothing new. Changing the default would inform
users about what's new while still allowing me to stay unbothered. No extra
setting needed. Why not do that?
Regards.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list