From: David Bremner <david@tethera.net>
To: "João Pedro" <jpedrodeamorim@gmail.com>,
"Jose A Ortega Ruiz" <jao@gnu.org>,
notmuch@notmuchmail.org
Subject: Re: Scheduling mails
Date: Thu, 04 Apr 2024 08:15:41 -0300 [thread overview]
Message-ID: <871q7lml9e.fsf@tethera.net> (raw)
In-Reply-To: <871q7lsuog.fsf@ergo>
João Pedro <jpedrodeamorim@gmail.com> 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=time properties (wildcard search is currently only supported
>> using s-exp queries).
>
> How about having a list of '(MESSAGE-ID . SCHEDULED-TIME), with the
> periodic check looking in that list for the scheduled times? It would
> have the issue of it not being persistent between Emacs sessions, but I
> think that could be addressed by letting the users know this lack of
> persistance, and documenting how you could achieve it with
> `savehist-additional-variables'.
One advantage of doing it outside emacs (in the notmuch database) is
that you could have the delivery also managed outside emacs. So cron /
systemd-timer / whatever. I guess the downside is it might be more work
to prototype.
\r
next prev parent reply other threads:[~2024-04-04 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <QgHQAeKcfzu4V_C0tkbpYXnzqYi9qt3ZvrB6ld7HkVYnD1tPjYaOTvwZZ9OEQVC8un-tb6uJflqJojN6lXLNJw==@protonmail.internalid>
2024-04-02 0:18 ` Scheduling mails João Pedro
2024-04-02 1:05 ` Jose A Ortega Ruiz
2024-04-02 4:34 ` João Pedro
2024-04-03 10:06 ` David Bremner
2024-04-04 2:55 ` João Pedro
2024-04-04 11:15 ` David Bremner [this message]
2024-04-04 16:38 ` Marc Fargas
2024-04-04 11:10 Marc Fargas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q7lml9e.fsf@tethera.net \
--to=david@tethera.net \
--cc=jao@gnu.org \
--cc=jpedrodeamorim@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).