From: Laura Conrad <lconrad@laymusic.org>
Subject: gnus-slave problem @)x_C2fgA~Wi&@/V"f6vs*B.1`(};T=]?M6O;HvGS
Date: Thu, 03 Jun 2004 11:01:30 -0400 [thread overview]
Message-ID: <874qps4red.fsf@tuba.localdomain> (raw)
I've been keeping a window open at work, with an ssh connection to my
machine at home where I get the home email. At home, I have an emacs
that stays on for weeks, with a frame running gnus, with lots of
groups for email and news.
At work, I've been invoking gnus-slave, and saving pretty often as the
connection goes down a couple of times a day.
This is working as I expected for mail -- in general, if I have either
saved before changing locations, or I read the auto-save file, I don't
end up reading the same email twice.
However, for news, I seem to have something screwed up. The home gnus
session never seems to see any that I haven't read any more, and the
work gnus-slave session always starts with all the news for the last
couple of weeks listed as unread.
The news that isn't being accounted for correctly is coming from a
server specified as:
(setq gnus-select-method '(nntp "bos.news.speakeasy.net"))
Am I doing something wrong?
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
reply other threads:[~2004-06-03 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=874qps4red.fsf@tuba.localdomain \
--to=lconrad@laymusic.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).