Iago-lito

> > the cost is that users should have an up-to-date copy of these sources to compile it, right? > > Sure, but that's no obstacle really. Indeed :) >...

Agreed on everything :) Thank you for feedback again. Let's pause this until I can pick this up, or someone else does.

(for future reference about this point specifically: > actually, even a C++ compiler's optimizer would probably fail to optimize that example down to `d = b;`, because if `a` and...

> those preconditions are huge, and Eidos has none of them Of course. Sorry, I haven't been accurate because I was hesitating between my willingness to "pause discussion" and the...

Hi @eirianop, nice to read you :) As I wrote, I won't have time to tinker about this any time soon, but I would be glad to find some by...

I'm curious about the use case / motivation for this. Can you not just set it off then on again 30 minutes later? (the advantage is that it'll fit exactly...

Okay I see. So you just choose whatever duration comfortably fits what you think you need as an `off` period. I have to admit that I would not use it,...

Thanks for the convincing insight @williamboman :) IIUC these workarounds will "make it work", but none solves the problem that the formatter is behaving incorrectly with the default installation. Do...

@exFalso Well, I used to think I liked the merged style, but I have to admit that you've just changed my mind :) I did not realize that *DRY actually...

Wops! Confirmed. I agree this wouldn't be consistent with other Vim operators, even though making it optionnal wouldn't change the default behavior. Sorry for the duplicate. To make use of...