Re: [PATCH] emacs: Add notmuch-show-local-dates option

2020-07-03 Thread Daniel Kahn Gillmor
On Thu 2020-07-02 18:02:34 -0400, Kevin Foley wrote: > Daniel Kahn Gillmor writes: >> and it could take three values: >> >> - nil (default), shows the Date: header as received >> - t, shows the timestamp from the Date: header in local time, >>with the as-received header in parens afterward

Re: introduce exception handling at top level of libnotmuch

2020-07-03 Thread David Bremner
Daniel Kahn Gillmor writes: > > I think this looks fine, and it isn't a huge amount of boilerplate. > > Please merge. > > --dkg OK, merged to master, thanks for the review. d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send

Re: [PATCH] emacs: Add notmuch-show-local-dates option

2020-07-03 Thread David Bremner
Daniel Kahn Gillmor writes: > But if the sender is in TZ=Europe/Berlin, i would see: > > Date: Fri, 03 Jul 2020 13:22:36 -0400 [Fri, 03 Jul 2020 19:22:36 +0200] > > (Note that RFC 5322 Date format shows the hour offset, but not the > actual TZ -- i can't tell from -0400 whether someone is in

Re: Feature freeze for notmuch 0.30: June 1

2020-07-03 Thread David Bremner
David Bremner writes: > I've tagged a 3rd release candidate (which is of course rc2, because > this week I belong to the cult of 0 based indexing). All of the blockers > I know of are fixed, and I'd consider us in "deep freeze", hopefully to > release in a week or so if there are no nasty bugs

Re: Newbie: On Outlook Exchange how to use notmuch to connect to it?

2020-07-03 Thread Georg Faerber
On 20-07-02 14:59:59, Daniel Kahn Gillmor wrote: > Notmuch only works with a local maildir. So what you need is a way to > get a copy of your messages from Exchange and build a local maildir. > > I'm afraid i don't have a good answer for that -- it will typically > depend on how Exchange is

Re: [PATCH] bindings/python-cffi: copy version file into bindings dir

2020-07-03 Thread David Bremner
David Bremner writes: > Attempt to avoid breaking "pip install ." > > As far as I can tell, we need to have a copy (not just a relative > symlink) of the version file. Applied, as part of 0.30~rc3. Let me know if this is still broken for pip users. I tried "pip install .", but that's all I

Re: [PATCH] doc: update name of gmime package to install

2020-07-03 Thread David Bremner
David Bremner writes: > Fedora still has an old gmime-devel which is 2.6.x. This is no longer > supported by notmuch. Applied, with s/yum/dnf/ in 0.30~rc3 d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to

Re: [PATCH] build: produce signatures for release candidate tarballs.

2020-07-03 Thread David Bremner
David Bremner writes: > Today Defalos on #notmuch asked for a signed tarball for > 0.30~rc2. This is a minimal change to support this in the future. The > question of automagically uploading will need more thought; currently > I like the fact that tags from pre-releases are only pushed

Re: [PATCH 1/2] configure: can gpgme can verify signatures when decrypting with a session key?

2020-07-03 Thread David Bremner
Daniel Kahn Gillmor writes: > If https://dev.gnupg.org/T3464 is unresolved in the version of gpgme > we are testing against, then we should know about it, because it > affects the behavior of notmuch. > series is applied as part of 0.30~rc3 d ___

Re: [RFC PATCH] lib: document new database_open API

2020-07-03 Thread David Bremner
David Bremner writes: > There is not much code to back this so far. This is just me thinking > out loud at this point. The location calculation is done (and also > easy). The challenging part is probably updating > notmuch_database_get_config to do what this comment promises. There's always

[RFC PATCH] lib: document new database_open API

2020-07-03 Thread David Bremner
Several aspects of this are potentially controversial: 1) The use of environment variables as fallback. I understand the discomfort with having a library function check the environment, but this seems to be functionality people want, and it is better to implement it once. 2) The use of both NULL