From: Colin Rafferty <craffert@ms.com>
Subject: Re: prolems viewing inline GIFS (XEmacs, 0.80)
Date: 12 Mar 1999 10:43:46 -0500 [thread overview]
Message-ID: <vgvoglyww5p.fsf@ms.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "12 Mar 1999 16:04:15 +0100"
Kai Grossjohann writes:
> Colin Rafferty <craffert@ms.com> writes:
>> However, if I tab to the button and hit `i' (`gnus-mime-inline-part'),
>> I get the raw GIF. Ugh!
>>
>> Is this a feature or a bug? Personally, I choose the latter.
> This is a feature. It allows you to look at textual stuff even if it
> has been declared as sumpin' strange, such as
> application/octet-stream, or image/gif, or message/rfc822.
That's legit.
> Hm. Maybe it had something to do with textual things with
> ``Content-Disposition: attachment'', too. I don't remember.
Yes, the disposition was `attachment'. This is the default in mml,
when I do a `C-c C-a'.
How can I change it so that disposition of pretty things are inline,
but ugly things are attachments? For example, a GIF is pretty, but a
.tar.gz is ugly.
I'm not sure where a patch or .el file falls into the pretty/ugly
hierarchy..
> Doesn't XEmacs already display things inline which it can display
> inline? Then you're using `i' for the wrong purpose.
It doesn't but not for disposition `attachment'.
--
Colin
next prev parent reply other threads:[~1999-03-12 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 14:02 Colin Rafferty
1999-03-12 15:04 ` Kai.Grossjohann
1999-03-12 15:43 ` Colin Rafferty [this message]
1999-03-14 16:16 ` Lars Magne Ingebrigtsen
1999-03-15 15:50 ` Colin Rafferty
1999-03-15 17:50 ` William M. Perry
1999-03-15 19:25 ` [patch] " Colin Rafferty
1999-03-28 15:06 ` 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=vgvoglyww5p.fsf@ms.com \
--to=craffert@ms.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).