Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: blokely@gmail.com
To: info-gnus-english@gnu.org
Cc: Reiner Steib <Reiner.Steib@gmx.de>
Subject: Re: Help with multipart/mixed messages
Date: 16 Feb 2007 11:22:16 -0800	[thread overview]
Message-ID: <1171653736.657689.249280@h3g2000cwc.googlegroups.com> (raw)
In-Reply-To: <v91wkrnpf2.fsf@marauder.physik.uni-ulm.de>


Reiner,

That worked perfectly - thank you very much.

Best wishes,

Bill

On Feb 15, 1:20 pm, Reiner Steib <reinersteib+gm...@imap.cc> wrote:
> On Mon, Feb 12 2007, blok...@gmail.com wrote:
> > `gnus-group-make-doc-group'.  When I open some of the groups, I see
> > something like:
>
> [...]
> > (In contrast, if I "mail -f" the file I made the doc group from, I
> > see 1500+ messages.)
>
> Use the prefix argument to force mbox:
>
> ,----[ (info "(gnus)Foreign Groups") ]
> | `G f'
> |      Make a group based on some file or other
> |      (`gnus-group-make-doc-group').  If you give a prefix to this
> |      command, you will be prompted for a file name and a file type.
> |      Currently supported types are `mbox', `babyl', `digest', `news',
> |      `rnews', `mmdf', `forward', `rfc934', `rfc822-forward',
> |      `mime-parts', `standard-digest', `slack-digest', `clari-briefs',
> |      `nsmail', `outlook', `oe-dbx', and `mailman'.  If you run this
> |      command without a prefix, Gnus will guess at the file type.  *Note
> |      Document Groups::.
> `----
>
> Bye, Reiner.
> --
>        ,,,
>       (o o)
> ---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

      reply	other threads:[~2007-02-16 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 21:05 blokely
2007-02-15 20:20 ` Reiner Steib
2007-02-16 19:22   ` blokely [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=1171653736.657689.249280@h3g2000cwc.googlegroups.com \
    --to=blokely@gmail.com \
    --cc=Reiner.Steib@gmx.de \
    --cc=info-gnus-english@gnu.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).