From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Questions about gnus
Date: Tue, 27 Aug 2002 12:14:29 -0400 [thread overview]
Message-ID: <m3elckmg78.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vaf3ct0pm4g.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 27 Aug 2002 13:38:39 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> Gnus normally doesn't like it if you use other tools behind its
> back. If you use the nnmh backend (slow!), you have the highest
> chance of it working.
nnmaildir is also intended to work this way.
> * If you manipulate messages behind Gnus' back, the Gnus-internal
> marks will not travel with the messages.
This isn't a problem with nnmaildir unless you move a message from one
group to another. But nnmaildir makes it easy for you to copy the
marks along with the message.
> * If you EVER reuse message numbers
This isn't a problem with nnmaildir, since filenames are different
from article numbers.
paul
prev parent reply other threads:[~2002-08-27 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 21:22 Xiaowei Yang
2002-08-27 11:38 ` Kai Großjohann
2002-08-27 14:10 ` Yair Friedman (Jerusalem)
2002-08-27 14:57 ` Kai Großjohann
2002-08-27 16:14 ` Paul Jarc [this message]
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=m3elckmg78.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--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).