In D24739#549483, @mlaurent wrote:

is it in all language we have Month + year ?

I have no idea

I wonder if the original way was done for translation purposes? In any event, I think relying on localization makes more sense.

I'm not sure I like this code.

Thanks to @montel for mentoring me :)

save/restore application settings

+1
will fix the problem I reported.

can you update the kmail docbook accordingly?

tested locally and it works fine!
+1 from me.

I have a folder that always goes into infiinite loop mode. I can test this

yay

should be ok.
no objections.

Yep. tested locally and fixes the problem

agree that fullName() -> aBetterName() change should go into a separate patch.
+1

also see this crash in impptest

I've also been seeing those test failures for a long time.
seems to break if you aren't in the CET timezone (or somesuch). Harmless, but annoying.

deprecate fullName() and replace with fullEmail()?

remove unnecssary clang-analyzer-optin.cplusplus.VirtualCall fixes and add NOLINT comments so clang-tidy ignores them

In D21036#461578, @dvratil wrote:

Well, technically, calling virtual methods from ctor in dtor in those particular cases is safe and your changes do not have any impact, since the standard says that when a ctor/dtor calls a virtual function of the object currently under construction/destruction the override called is that of the current ctor's/dtor's class - in other words, it will never call an override in a more-derived class (and calling an override in a superclass is safe, because that one is already constructed/not yet destroyed). This would only be a problem (or undefined behavior, rather) if any of those methods were pure virtual, which they are not so this might be considered a false-positive from clazy.

Edit: there's also some trickyness in this when non-linear inheritance in involved, but that's not the case here either.

ping

Pino's suggestion
added tests

I'll assume you rebuilt all of kde pim ok

missing changes for QLatin1String()
thanks for noticing Achim

Dan's comments and suggestions

I will fix those 'auto' variables. I had planned a clang-tidy round of cleanups, but I can do the auto stuff here.
your other suggestions are also good. I'll handle them.

yes please

remove commented out lines I added during testing

goodie

I'm for this.
I never created such a patch because I wasn't sure what minimum version was needed.

I applied this patch locally for testing. so far so good.

this would be a nice addition to Krazy. on my todo list.

do you have commit access? If not I can commit for you

do you have commit access? If not I can commit for you