From: Lee Willis <lee@gbdirect.co.uk>
Subject: MIME problems in 0.32
Date: 24 Sep 1998 09:42:50 +0100 [thread overview]
Message-ID: <lzww6tx5o5.fsf@landlord.gbdirect.co.uk> (raw)
Hmm, I've applied Shu's patches but there are still some bugs in the
MIME handling.
a) The size of parts no longer shows up correctly in MIME buttons (It's
always 0)
b) When you click a button which spawns an external process to view an
image you get dumped into the buffer *mm* instead of staying in the
Article buffer where you were (Presuming you clicked enter not a
mouse button (My mouse only has buttons 1 and 3 :( ))
The not decoding problem seems to have gone away though :)
Cheers
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next reply other threads:[~1998-09-24 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-24 8:42 Lee Willis [this message]
1998-09-24 17:11 ` 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=lzww6tx5o5.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).