From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: rebuilding .overview
Date: 11 Feb 1997 13:43:39 +0100 [thread overview]
Message-ID: <m27mkfqzr8.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Michael Lamoureux's message of 10 Feb 1997 12:33:11 -0500
Michael Lamoureux <lamour@engin.umich.edu> writes:
> Also, after running the above function all of the new messages (there
> were 105 new messages, which is how I noticed there was a problem in
> the first place), all of the messages that were added back into the
> .overview file were given a mark of read instead of unread. I had to
> enter the group with C-u Ret to see them. Is that the best default
> mark to have for such an operation?
I can't explain this. Regenerating the .overview files doesn't affect
article readedness at all -- all that's being handled by Gnus, and
Gnus knows nothing about .overview files and stuff like that.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-02-11 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-10 17:33 Michael Lamoureux
1997-02-10 19:45 ` Rich Pieri
1997-02-12 1:31 ` Michael Lamoureux
1997-02-11 12:43 ` Lars Magne Ingebrigtsen [this message]
1997-02-11 20:21 ` Michael Lamoureux
1997-02-12 8:50 ` Lars Magne Ingebrigtsen
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=m27mkfqzr8.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.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).