From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Sharing gnus between 2 machines
Date: Tue, 9 Jul 2013 17:50:44 +0100 [thread overview]
Message-ID: <87fvvnoexn.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87txk4t2pi.fsf@free.fr> (Julien Cubizolles's message of "Tue, 9 Jul 2013 13:03:37 +0200")
Julien Cubizolles <j.cubizolles@free.fr> writes:
[...]
> What confusion does the agent exhibit. For me, it's mostly the
> read/old/expired statuses that gets messed up.
Yes, this is one confusion. Another is that an article will become
inaccessible, as if I were unplugged and trying to access an article
that had not been downloaded. When I try to access the article, gnus
tells me it has marked it for downloading, even when I am plugged in,
and never does download it. Very strange. I can read most articles not
yet downloaded so long as I am plugged in but not always.
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.3.50.1 + Ma Gnus v0.8 + evil 1.0.5
: BBDB version 3.02 ($Date: 2013/05/15 13:17:58 $)
next prev parent reply other threads:[~2013-07-09 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871u7fbmtv.fsf@free.fr>
2013-07-05 9:11 ` Eric S Fraga
2013-07-09 11:03 ` Julien Cubizolles
2013-07-09 16:50 ` Eric S Fraga [this message]
2013-07-09 18:09 ` Julien Cubizolles
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=87fvvnoexn.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).