From: Michael R Cook <mcook@cognex.com>
Subject: gnus-slave
Date: 03 Oct 1996 11:30:30 -0400 [thread overview]
Message-ID: <r4ybho6p61.fsf_-_@cognex.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 02 Oct 1996 01:02:20 +0100
Shouldn't `gnus-slave' read any existing slave files?
If I start `gnus-slave', read a few articles, and exit gnus, if I then start
`gnus-slave' again, the articles I read are presented to me again as being
unread.
I would think starting up `M-x gnus-slave' should happen exactly as `M-x gnus'
does, except that `gnus-slave' would not delete the slave files.
No?
Michael.
next reply other threads:[~1996-10-03 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-03 15:30 Michael R Cook [this message]
1996-10-04 6:44 ` gnus-slave Lars Magne Ingebrigtsen
2002-04-23 16:42 gnus-slave Harry Putnam
2003-01-01 20:20 ` gnus-slave Lars Magne Ingebrigtsen
2005-02-16 18:16 gnus-slave Harry Putnam
2005-02-16 18:42 ` gnus-slave Harry Putnam
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=r4ybho6p61.fsf_-_@cognex.com \
--to=mcook@cognex.com \
/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).