From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Delayed email sent 26 times
Date: Sat, 13 Aug 2011 09:20:17 +0200 [thread overview]
Message-ID: <87obzt4w26.fsf@topper.koldfront.dk> (raw)
Hi.
I rarely send delayed emails, but yesterday I delayed an email with C-c
C-j for sending this morning at 08:00.
When I started Gnus, after 08:00, it sent the email allright. But it did
so 26 times!
Each email has a new Message-ID and the Date:s are ~3 seconds apart.
WTF?
I have a function added to my message-send-hook that takes a while¹ (it
tries to fetch the currently playing song from my jukebox, which was
turned off at the time - so mpc had to time out).
Could it be that Gnus doesn't keep track of which delayed emails are
currently being processed, and if it takes a while, the email is sent
again, and again, and again until the first/"quickest" attempt succeeds?
Just wondering.
Best regards,
Adam
¹ ; Include X-Now-Playing:
(defun asjo-mpd-now-playing ()
"Returns a string with the song currently playing on the mpd"
(interactive)
(save-excursion
(setenv "MPD_HOST" asjo-mpd-host)
(let* ((string (shell-command-to-string (concat "mpc" asjo-mpc-format))))
(string-match "[^/]*$" string)
(match-string 0 string))))
(defun asjo-add-now-playing-header ()
"Add X-Now-Playing header"
(let ((now-playing (asjo-mpd-now-playing)))
(when (not (string-match "error" now-playing))
(message-add-header (concat "X-Now-Playing: " now-playing))
(message "Updated: %s" now-playing))))
;; Insert header:
(add-hook 'message-setup-hook 'asjo-add-now-playing-header)
--
"riverrun, past Eve and Adam's, from swerve of shore Adam Sjøgren
to bend of bay, brings us by a commodius vicus of asjo@koldfront.dk
recirculation back to Howth Castle and Environs."
next reply other threads:[~2011-08-13 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 7:20 Adam Sjøgren [this message]
2011-08-17 0:11 ` Katsumi Yamaoka
2011-08-17 8:15 ` Adam Sjøgren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obzt4w26.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).