From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Questions about gnus
Date: Tue, 27 Aug 2002 13:38:39 +0200 [thread overview]
Message-ID: <vaf3ct0pm4g.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <200208262122.g7QLMNxU008098@cordelia.lcs.mit.edu> (Xiaowei Yang's message of "Mon, 26 Aug 2002 17:22:23 -0400")
Xiaowei Yang <yxw@mit.edu> writes:
> I am looking for a thread-based mailer read and want to know whether
> GNUS is the right choice for me. I am an mh-e user. Thus, I would like
> to run the mailer in emacs, as well as using mh-e's command line
> interfaces such as "pick", "scan". I also want to use BBDB. Can
> someone on this list give me a clue whether GNUS is the right one?
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. I think in that case, you only need to be
aware of the following:
* If you manipulate messages behind Gnus' back, the Gnus-internal
marks will not travel with the messages.
* If you EVER reuse message numbers (eg, by deleting the last msg in
a folder and then putting a new message into the folder which then
gets the same number as the previously-deleted message), then Gnus
will get REALLY REALLY confused. If the previous message was read,
then Gnus will think the new message is read, and so on.
DON'T DO THAT.
With these caveats, it might work.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2002-08-27 11:38 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 [this message]
2002-08-27 14:10 ` Yair Friedman (Jerusalem)
2002-08-27 14:57 ` Kai Großjohann
2002-08-27 16:14 ` Paul Jarc
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=vaf3ct0pm4g.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).