On Sat 2019-12-28 10:01:17 -0500, William Casarin wrote:
> These patches bring notmuch-tree more in line with the user experience
> of notmuch-show by adding the x/X bindings.
It looks like this series has been reviewed by dme, and is presumably
approved by him, with the exception of patch 3/7,
On Thu 2020-02-20 19:16:23 +0100, Reto wrote:
> On 20 February 2020 18:18:52 CET, Daniel Kahn Gillmor
> wrote:
>>if you have a read/write DB, then the changes you make to the DB are
>>also visible, right? it's not a static snapshot in that sense.
>
> Ehm, not the behavior I've seen while I was
Sean Whitton writes:
> So, your hypothesis is that notmuch is opting not to add the Seen flag
> in order to avoid having to move the message from new to cur, for the
> sake of mutt, but that's a bug because I've explicitly requested adding
> Seen, so it ought to go ahead and move it from new to
Hello David,
Thank you for your reply.
On Thu 20 Feb 2020 at 08:22AM -04, David Bremner wrote:
> Sean Whitton writes:
>
>> I have this in my post-new hook:
>>
>> notmuch tag -unread -- folder:sent
>>
>> The idea is that copies of my sent mail which get returned to me and
>> stored in my
On Sun 2020-01-12 17:13:59 +0200, Tomi Ollila wrote:
> But, if we already made Xapian 1.4 minimun requirement in the next notmuch
> release, there XAPIAN_FIELD_PROCESSOR is always supported and all these
> conditionals could be removed (before even adding new)...
I'd support making Xapian 1.4 a
On Thu 2020-02-13 19:13:51 -0400, David Bremner wrote:
> Peter Wang writes:
>
>> In particular, timestamps beyond 2038 could overflow the sprinter
>> interface on systems where time_t is 64-bit but 'int' is a signed 32-bit
>> integer type.
>
> Series pushed to master.
I'm a bit slow following up
On 20 February 2020 18:18:52 CET, Daniel Kahn Gillmor
wrote:
>if you have a read/write DB, then the changes you make to the DB are
>also visible, right? it's not a static snapshot in that sense.
Ehm, not the behavior I've seen while I was testing it out, but that may have
been my fault then?
On Thu 2020-02-13 22:11:27 +0100, Reto wrote:
> I'm trying to use the notmuch C library in a mail client.
> Now, I learned that an open DB is essentially a snapshot at the time of
> opening.
> If I want the current state of the notmuch DB, I need to reopen the DB.
if you have a read/write DB,
David Bremner writes:
>> This works:
>>
>> notmuch tag +unread -- folder:sent
>> notmuch tag -unread -- folder:sent
>>
>> Is there some more elegant way to force a sync of maildir flags? Am I
>> the only one that has copies of my own mail in my inbox folder, not
>> marked as read from
Sean Whitton writes:
> I have this in my post-new hook:
>
> notmuch tag -unread -- folder:sent
>
> The idea is that copies of my sent mail which get returned to me and
> stored in my inbox, e.g. by mailing lists, would get maildir Seen tags
> added to them. But that does not happen.
I
10 matches
Mail list logo
