From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Can a mail-sources :prescript communicate progress back to the user?
Date: Wed, 11 Apr 2018 21:33:26 +0200 [thread overview]
Message-ID: <87bmeptu61.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87sh813bkx.fsf@mouse.gnus.org>
Lars writes:
> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>> I am wondering whether there is any functionality for a :prescript in
>> mail-sources to report progress back to the user - e.g. by messages
>> being shown in the mini-buffer?
>
> Yes... can't you just use a prescript like, er,
>
> :prescript (lambda () (message "Before fetching..."))
>
> or something?
Hm, yes, I guess I could made my :prescript a (defun) that calls the
Python script and reads stdout, (message)'ing every line...
Thanks for the pointer!
Best regards,
Adam
--
"I'm only civil because I don't know any swear words." Adam Sjøgren
asjo@koldfront.dk
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2018-04-11 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 12:11 Adam Sjøgren
2018-04-11 17:19 ` Lars Ingebrigtsen
2018-04-11 19:33 ` Adam Sjøgren [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmeptu61.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).