Hi there,
> I might be wrong, but I don't think the Gnus agent can be easily reused
> from notmuch. We could perhaps save the message as a draft upon C-c C-j,
> and then have a periodic timer that checks if any of the drafts has
> expired (maybe using a special, additional tag for the search) and
Dmitry Bogatov writes:
> Some people (e.g: me) prefer to read their email with threaded
> representation by default.
>
Applied to master.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.o
jli...@fsfe.org writes:
>
> ;;; _
> -
> +;;;#autoload
> (define-mail-user-agent 'notmuch-user-agent
>'notmuch-mua-mail
>'notmuch-mua-send-and-exit
Applied to master with the deleted blank line put back
___
notmuch mailing list -- notmuch@not
Hi all,
El dom. 24 de mar. 2024, Marc escribió:
> I am attaching a new patch that includes an additional test on
> T630-emacs-draft.sh.
>
> On the test only `References` is at the top (hence hidden by emacs), not
> `In-Reply-To`. I guess that does rely on some configuration.
>
> In any case, the t
Hi there,
> I might be wrong, but I don't think the Gnus agent can be easily reused
> from notmuch. We could perhaps save the message as a draft upon C-c C-j,
> and then have a periodic timer that checks if any of the drafts has
> expired (maybe using a special, additional tag for the search) and
João Pedro writes:
> Ah, indeed message properties seem to be more appropriate. Are they
> persisted, or are they tied to an Emacs session?
They are persisted in the database, and backed up with notmuch dump.
>
>> but your periodic search would still have to search for all of the
>> scheduled=ti
