Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Setting up select methods to read from a directory of mbox files
Date: Sun, 21 Jul 2002 11:08:09 +0200	[thread overview]
Message-ID: <vaffzydo3d2.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <u1mu31ch.fsf@morpheus.demon.co.uk>

Paul Moore <gustav@morpheus.demon.co.uk> writes:

> It's sort of what I want - I had a go with it. The problem is that it
> doesn't recognise the mbox files in the directory as such, and so they
> look like simple mail messages, rather than like groups.

Argh.  This should be changed.  I don't have the time to do it,
though.  Sorry.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)


      parent reply	other threads:[~2002-07-21  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y9c72yrf.fsf@morpheus.demon.co.uk>
     [not found] ` <vafk7nqn0qh.fsf@lucy.cs.uni-dortmund.de>
2002-07-20 14:45   ` Paul Moore
2002-07-20 16:11     ` Josh Huber
2002-07-20 21:23       ` Paul Moore
2002-07-21  9:08     ` Kai Großjohann [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=vaffzydo3d2.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).