From: Steinar Bang <sb@dod.no>
Subject: Re: No Gnus feature request: simpler file structure for synching
Date: Thu, 08 Jan 2004 20:49:45 +0100 [thread overview]
Message-ID: <87u1362pba.fsf@doohan.bang.priv.no> (raw)
In-Reply-To: <87isjn1whw.fsf@emptyhost.emptydomain.de>
>>>>> Kai Grossjohann <kai@emptydomain.de>:
> That's why I suggested to port the .marks code to nntp.el; then you
> would have a file for each NNTP server which records only which
> articles have been read on that NNTP server. That file could then
> be synced.
I would like that very much. Eg. I read news.gmane.org both at home
and and work, while the USENET servers are different. I would like to
avoid having to skim through the same gmane groups twice.
A problem though, is that the set of groups I see at home is different
than the set of groups I see at work (though there is a non-empty
intersection of the two).
Is there some way to cater for this? Or will I have to subscribe to
the same set of gmane groups both places?
next prev parent reply other threads:[~2004-01-08 19:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 0:24 No Gnus feature request: simpler file structure for synching between two machines John Owens
2004-01-07 7:22 ` No Gnus feature request: simpler file structure for synching Matt Armstrong
2004-01-07 8:27 ` Steve Youngs
2004-01-07 12:44 ` Kai Grossjohann
2004-01-07 14:28 ` Reiner Steib
2004-01-07 14:59 ` Kai Grossjohann
2004-01-07 17:42 ` nnir problems (was: No Gnus feature request: simpler file structure for synching) Reiner Steib
2004-01-07 16:20 ` No Gnus feature request: simpler file structure for synching Steven E. Harris
2004-01-08 22:23 ` Reiner Steib
2004-01-08 22:51 ` Steven E. Harris
2004-01-08 22:58 ` Paul Jarc
2004-01-07 17:07 ` John Owens
2004-01-07 17:47 ` Kai Grossjohann
2004-01-07 19:17 ` Josh Huber
2004-01-07 21:32 ` Simon Josefsson
2004-01-08 19:49 ` Steinar Bang [this message]
2004-01-11 21:49 ` Kai Grossjohann
2004-01-12 22:15 ` Steinar Bang
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=87u1362pba.fsf@doohan.bang.priv.no \
--to=sb@dod.no \
/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).