From: Jack Twilley <jmt+usenet@nycap.rr.com>
Subject: Re: [pgnus v0.66] Recursive MIME problem
Date: Mon, 04 Jan 1999 18:59:23 GMT [thread overview]
Message-ID: <m3pv8u9851.fsf@dt01q0n13.nycap.rr.com> (raw)
In-Reply-To: <86btkf75k9.fsf@slowfox.cs.uni-dortmund.de>
>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Jack> (how can I look at dirty pictures if you don't fix this?)
Kai> You can type C-d on such a message, then easily look at the
Kai> pictures in there.
Doh. I never thought of it as a digest. That works beautifully
recursively. Thanks.
I still think it's a bug that the other way doesn't work.
Thanks!
Jack.
(happy picture boy)
.
next prev parent reply other threads:[~1999-01-04 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-04 0:04 Jack Twilley
1999-01-04 9:25 ` Kai.Grossjohann
1999-01-04 18:59 ` Jack Twilley [this message]
1999-01-11 1:03 ` 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=m3pv8u9851.fsf@dt01q0n13.nycap.rr.com \
--to=jmt+usenet@nycap.rr.com \
/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).