Nice talk, just watched it.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 25 2017
In T3206#99005, @werner wrote:1.4 has build fixes for NetBSD. Thus I _assume_ this bug has been fixed.
@aa can you please try npth 1.5 ?
I think this is a duplicate of T2416 please let me know if you still see the crash with the current beta / release candidate of gpg4win-3.0
This is fixed now with ef038f2d1db15ef14c238137c1c42a99bbe25f42 initially we only took the first attachment. Now we check for the position of the created MOSS attachment. This explains why a second try worked because the MOSS was already created.
This is what you get if you "show source" in Outlook so it's only the headers.
Aug 24 2017
Avoid moving the window ourselves if the cursor happens to be on the same monitor than the currently focused window, since in that case the window will already be on the right monitor.
Is that really the entire mail? I can see only the header of the mail but not the body. How did you copy the raw mail?
I am not sure I agree with the “cryptic error message” bit. I would think anyone knowledgeable enough to play with LC_ALL (or any other LC_* variable) should understand what “a locale function failed” means and conclude that maybe the best way to fix the problem is to leave LC_ALL alone.
Please see my comments on rM9f24e6c9010e171fd11c5cdac797cb8ce2e501dd
It would also be good to explain the relation ship of this feature and the gpgme_get_dirinfo - if there is any
I merely said, that we won't replace libtool by the upstream version because that lacks other important changes we need. Upstream was not willing to integrate our changes for Windows support and also introduced a lot of other regressions as well as dropping support for some platforms. Thus we need to maintain our version.
Aug 23 2017
Is this even something that we can control?
I just realized that my fix for T3253 was incomplete, it only works if grabbing is enabled. With GnuPG Agent not requesting grabbing by default since 2.1.23, that would make the fix useless in the default configuration. Coming with a new patch soon...