From: Ishe Chinyoka <ishechinyoka@yahoo.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Autorefresh buffer at set interval
Date: Fri, 22 Apr 2022 04:21:44 +0200 [thread overview]
Message-ID: <87mtgdvow7.fsf@chinyoka.com> (raw)
In-Reply-To: <877d7ili8n.fsf@tethera.net>
Thanks David for the pointer to the timer documentation in the Elisp
manual. I successfully wrapped the refresh function in the
run-with-timer, such that every 15 minutes I automatically check for new
mail. The setup now works like a charm.
Thanks once again.
Ishe
David Bremner <david@tethera.net> writes:
> Ishe Chinyoka <ishechinyoka@yahoo.com> writes:
>
>> I am sorry if this is in the documentation, but I am failing to pick
>> the right spot. Anyway, which variable can I set to have notmuch-poll
>> triggered at a set interval?
>
> I don't think this currently exists. You could define your own timer
> [1].
>
>> BTW, I am on Arch and am running the Offlineimap as a systemd timer to
>> pull my messages every fifteen minutes. I also have a Notmuch script
>> under the ~/.mail/.notmuch/hooks/ that runs every time offlineimap
>> completes the refresh. My problem is now that after all this, I can't
>> seem to have the Notmuch emacs interface update automatically without me
>> doing a manual refresh with "G" keystroke.
>
> I suspect you only need "g" rather than "G", if you are already running
> notmuch new via a hook.
>
>> This morning I tried putting
>> notmuch-poll-and-refresh-this-buffer as a function in the notmuch-hello
>> hooks.
>
> You may want the function notmuch-refresh-all-buffers; that could go in
> your timer.
>
> [1]: (info "(elisp) Timers")
>
prev parent reply other threads:[~2022-04-22 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zgkmcwc0.fsf.ref@chinyoka.com>
2022-04-15 13:25 ` Autorefresh buffer at set interval Ishe Chinyoka
2022-04-21 12:43 ` David Bremner
2022-04-22 2:21 ` Ishe Chinyoka [this message]
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=87mtgdvow7.fsf@chinyoka.com \
--to=ishechinyoka@yahoo.com \
--cc=david@tethera.net \
--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).