From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: What's your gnus-demon-scan-news idle time?
Date: Fri, 25 Oct 2019 17:49:48 +0200 [thread overview]
Message-ID: <87o8y4akpv.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <xuu636fgomyx.fsf@ucl.ac.uk>
Eric writes:
> On Friday, 25 Oct 2019 at 15:27, Adam Sjøgren wrote:
>> I wanted to continue to use nnml, and I didn't want to read all emails
>> twice, so I found this hybrid setup which works pretty well for me.
>
> Yes, I have the same desire. I'm comfortable with splitting so I think
> I will give this a go. May therefore need to start using the demon...
Here's the code for the split I use:
(defun resend-to-mobile-split (resend-to)
"Call this as a fancy split to resend the message and continue (the split doesn't match anything, so splitting continues.)"
(save-excursion
(save-restriction
(if asjo-fetch-was-manual
(message "Not sending to mobile; user fetch")
(resend-to-mobile resend-to))
nil)))
(defun resend-to-mobile (resend-to)
"Actually resend the message."
(message "Resending to mobile; automatic fetch")
(widen)
(message-resend resend-to))
In case you want compare what you come up with with my crude implementation.
:-),
Adam
--
"Is my microphone on? Can you hear me?" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2019-10-25 15:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 4:34 dick.r.chiang
2019-10-24 5:35 ` Eric S Fraga
2019-10-24 13:55 ` Jorge A. Alfaro-Murillo
2019-10-24 14:17 ` Gijs Hillenius
2019-10-24 21:08 ` Adam Sjøgren
2019-10-25 12:59 ` Eric S Fraga
2019-10-25 13:27 ` Adam Sjøgren
2019-10-25 15:37 ` Eric S Fraga
2019-10-25 15:49 ` Adam Sjøgren [this message]
2019-10-27 15:33 ` Eric S Fraga
2019-10-24 23:30 ` Bob Newell
2019-10-25 1:42 ` Eric Abrahamsen
2019-10-25 2:06 ` dick
2019-10-25 3:10 ` Eric Abrahamsen
2019-10-31 13:36 ` Lars Ingebrigtsen
2019-11-14 2:54 ` Wrong default NNIR search method Spenser Truex
2019-11-14 18:51 ` Eric Abrahamsen
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=87o8y4akpv.fsf@tullinup.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).