From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: diret imap and agentised imap in sync
Date: Wed, 04 Sep 2002 21:16:36 +0200 [thread overview]
Message-ID: <vafelc9zht7.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87admx62vx.fsf@pale.loc> (Alexander Kotelnikov's message of "Wed, 04 Sep 2002 22:11:46 +0400")
Alexander Kotelnikov <sacha@giotto.sj.ru> writes:
> It seems it works better if I
> 1. Set gnus plugged ('J j')
> 2. Check groups ('g')
> 3. Fetch groups ('J s')
> 3. unplug gnus and read news
>
> But it is much more comfortable to keep gnus always unplugged and
> fetch articles with external program.
Aha! Now it rings a bell with me. Ages ago I wrote the following
(now probably quite outdated) function to fetch news/mail for me:
(defun kai-gnus-agent-do ()
(let ((gnus-verbose 5))
(message "Kai: fetching Agent session.")
(flet ((y-or-n-p (prompt) t)
(yes-or-no-p (prompt) t))
(gnus-agent-batch))
;(gnus-agent-fetch-session)
(message "Kai: starting Gnus")
(gnus)
(message "Kai: sending drafts")
(gnus-group-send-drafts)
(message "Kai: synchronizing flags")
(gnus-agent-synchronize)
(message "Kai: fetching agent stuff")
(gnus-agent-batch)
(message "Kai: exiting Gnus")
(gnus-group-exit)
(save-buffers-kill-emacs t)))
I called this function from "emacs -batch" (I think). (Now I don't
use it anymore.) It seems that I'm doing what you discovered is
necessary. Maybe the gnus-agent-batch function should be augmented to
do what the above does.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
prev parent reply other threads:[~2002-09-04 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 13:49 Alexander Kotelnikov
2002-09-03 15:44 ` Kai Großjohann
2002-09-03 18:32 ` Alexander Kotelnikov
2002-09-03 16:22 ` Simon Josefsson
2002-09-03 18:30 ` Alexander Kotelnikov
2002-09-03 20:28 ` Kai Großjohann
2002-09-04 18:11 ` Alexander Kotelnikov
2002-09-04 19:16 ` Kai Großjohann [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=vafelc9zht7.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).