From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Problems with inlining images in Emacs 20
Date: Thu, 26 Jul 2001 14:54:28 -0700 [thread overview]
Message-ID: <2n1yn3cq5n.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <m33d7jtrza.fsf@barry_fishman.att.net> (Barry Fishman's message of "Thu, 26 Jul 2001 15:23:05 -0400")
Barry Fishman <barry_fishman@acm.org> writes:
> I'm not an expert at gnus mime processing but:
>
> Concerning mm-decode.el:
>
> It seems wrong to put the image file wildcard "image/.*" as a part of
> mm-inlined-types. This seems to mean that any image type not caught
> by the mm-inline-media-tests will be just placed inline. Shouldn't
> one assume that if an image is not of a known type, the Emacs 21's
> will probably not know what to do with it, and if they did, at least
> the mm-valid-and-fit-image-p test should be made.
Emm. I think the recent change of "Default to displaying as text"
causes the problem. I've fixed it.
> In Emacs 20, inlined images do not look very pretty, and since they
> are inlined there isn't even a button to save them to a file or even
> get rid of them. This is a real pain.
> Concerning gnus-art.el:
>
> In gnus-display-mime, The mm-dissect-buffer test is always done in its
> strict mode. There seems to be messages that get correctly dissected
> with the strict option off, but using
>
> (or (mm-dissect-buffer) (mm-uu-dissect) (mm-dissect-buffer t))
>
> about line 3776 seems to cause emacs to break (although not to crash).
> Is this why strict mime processing is not a customization option?
I don't think so. Forcing to dissect a non-strict mime message may
causes some unexpected troubles.
> I have been working on a `gnus-force-mime' which can be called
> interactively, when you are seeing a message which is obviously
> intended to be mime, but is missing something like a mime version
> header. It would be available like "C-u g" which in a sense does the
> opposite in shutting off all processing. Does this seem reasonable?
> Is something like this already done?
`K m' repairs it.
> In general:
>
> I don't like encouraging the use of invalidly formatted mime messages,
> by just having mail/news readers accept them without comment.
> However, I can't just ignore mail that is incorrectly formatted, and
> disassembling them by hand is a real pain.
`K m', `W 6', `W q' and `W h' are designed for this purpose.
ShengHuo
next prev parent reply other threads:[~2001-07-26 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 19:23 Barry Fishman
2001-07-26 21:54 ` ShengHuo ZHU [this message]
2001-07-27 0:49 ` Barry Fishman
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=2n1yn3cq5n.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).