Jonathan Wakely

This matches the API of POSIX execv: https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html

The example is correct. The first argument to the ipstream constructor is the name of the executable to run (which will be looked up in PATH). The argv strings are passed to the new process as its argv[] array. By convention, argv[0] is the name of the executable that was run, but it doesn't have to be. You can actually pass some other string in argv[0]. So it's correct that there are two "rm" strings. One is used by the OS to find the program to run, and the other is passed to that program as its...

Patch autoconf fragments for C99 compatibility

a more elegant approach would be storing the pointer directly and using the right free() function later. The memory returned from the libsecret API is in memory anyway, so I don't think doing that would make any difference. The approach in my patch seems consistent with the handling of keys from the macOS keychain, and all other approaches in ensure_password. I could add a comment to my new code, but it seems like a pre-existing problem with ensure_password and not introduced by my changes. the relatively...

Small bugfix, the error string on a failed lookup was missing a newline.

Oh, I just used the default milestone of 1.5.0 for this ticket, without realising there's also a 1.4.5 milestone. That would be better IMHO :-) If this gets merged upstream I'd like to package it for Fedora, so getting it in the next release would be nice. It's a new feature but it's a pure extension with no impact on any existing features, so would be nice to have ASAP.

Related: https://sourceforge.net/p/isync/mailman/isync-devel/thread/CAHaCNWJpjM86a2sWK6Q-NYNgEwLECeXONhUcLCSV7BRP%2B0v79Q%40mail.gmail.com/#msg36608784 I suppose I could/should have added something about this to src/mbsyncrc.sample but the man page seems like a better place to put it.

Obtain passwords from GNOME Keyring