From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: mime problem
Date: 06 Apr 2000 00:39:49 +0200 [thread overview]
Message-ID: <vafvh1wp3yi.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: lconrad@world.std.com's message of "05 Apr 2000 14:45:10 -0400"
lconrad@world.std.com writes:
> When I get the message, I see text that looks to me like mime headers,
> but that doesn't seem to buttonize like mime headers in gnus, or to be
> decoded into separate parts by "metamail -w". I never see anything
> resembling a gif.
Right. Hm. Could a digest type be added to nndoc for this kind of
thing? That would be cool.
Try typing `A D' (or C-d?) on the message and have a look at the
central part. Maybe if nndoc grokked that, too, it would be really
useful?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-04-05 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 18:45 lconrad
2000-04-05 19:14 ` Kai Großjohann
2000-04-05 19:30 ` Alan Shutko
2000-04-05 22:40 ` Kai Großjohann
2000-04-05 22:39 ` Kai Großjohann [this message]
2000-04-06 14:31 ` Laura Conrad
2000-04-20 0:40 ` Lars Magne Ingebrigtsen
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=vafvh1wp3yi.fsf@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).