From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: broken nnfolder group
Date: Thu, 25 Jun 1998 00:43:36 +0200 [thread overview]
Message-ID: <m3af725skn.fsf@sparky.gnus.org> (raw)
In-Reply-To: Robert Epprecht's message of "24 Jun 1998 14:33:16 +0200"
Robert Epprecht <epprecht@logon.ch> writes:
> No, they where not moved, but *deleted*. I have searched them to find out
> if I hadn't moved them by error, but they are gone. Even if I would have
> deleted them this wouldn't explain the fact, that the new article, which
> I moved into the group after the incident as a test, was not visible there
> until I quit Gnus and restarted it.
Well, Gnus generally doesn't know about articles until you request
Gnus query the backends for info. Moving an article to a group will
not make Gnus aware that the group has a new article.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-06-24 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-22 9:10 Robert Epprecht
1998-06-24 4:45 ` Lars Magne Ingebrigtsen
1998-06-24 12:33 ` Robert Epprecht
1998-06-24 22:43 ` Lars Magne Ingebrigtsen [this message]
1998-06-27 19:56 ` Robert Epprecht
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=m3af725skn.fsf@sparky.gnus.org \
--to=larsi@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).