From: William Goedicke <goedicke@world.std.com>
Cc: ding@gnus.org
Subject: Re: "no unread news"
Date: 12 Jul 2002 13:23:16 -0400 [thread overview]
Message-ID: <m3y9cgrhbv.fsf@nuthatch.booksonbits.com> (raw)
In-Reply-To: <vafznwwx5v5.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Dear Kai -
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Do you have a ".marks" file in that group?
I don't, but you sent me in the right direction. There was a hidden
file in the directory called .overview mving it did the trick.
--
Yours - Billy
============================================================
William Goedicke goedicke@world.std.com
http://world.std.com/~goedicke
============================================================
Lest we forget:
The Computer Professional's Credo: "First do no harm."
- William Goedicke
next prev parent reply other threads:[~2002-07-12 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 19:37 William Goedicke
2002-07-11 19:44 ` Paul Jarc
2002-07-11 20:32 ` William Goedicke
2002-07-12 16:08 ` William Goedicke
2002-07-12 16:34 ` Kai Großjohann
2002-07-12 17:23 ` William Goedicke [this message]
2002-07-13 10:21 ` Kai Großjohann
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=m3y9cgrhbv.fsf@nuthatch.booksonbits.com \
--to=goedicke@world.std.com \
--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).