From: Hamish Macdonald <hamishm@lucent.com>
Subject: Re: MIME attachments?
Date: 15 Jun 1999 11:45:59 -0400 [thread overview]
Message-ID: <6w674pa2mg.fsf@lucent.com> (raw)
In-Reply-To: Hamish Macdonald's message of "15 Jun 1999 11:34:06 -0400"
>>>>> On 15 Jun 1999 11:34:06 -0400,
>>>>> In message <6wemjd32c1.fsf@lucent.com>,
>>>>> I wrote:
Hamish> Definately some sort of screwy XEmacs thing. When
Hamish> insert-file-contents returns, the buffer the file was inserted
Hamish> into is read-only. When mm-encode-content-transfer-encoding
Hamish> calls base64-encode-region, it calls (point-min) and
Hamish> (point-max) to get the bounds of the temp buffer. These both
Hamish> return 1. Yet when I switch to the temp buffer, the GIF is
Hamish> visible as an inline gif. XEmacs should just insert the
Hamish> contents, no?
0.84 uses insert-file-contents-literally
0.88 uses insert-file-contents
insert-file-contents-literally does the right thing.
next prev parent reply other threads:[~1999-06-15 15:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-15 14:32 Hamish Macdonald
1999-06-15 14:46 ` Norman Walsh
1999-06-15 14:53 ` Hamish Macdonald
1999-06-15 14:58 ` Hamish Macdonald
1999-06-15 15:34 ` Hamish Macdonald
1999-06-15 15:45 ` Hamish Macdonald [this message]
1999-06-15 15:58 ` William M. Perry
1999-06-15 16:05 ` Alexandre Oliva
1999-06-15 16:11 ` Didier Verna
1999-06-15 16:11 ` Hrvoje Niksic
1999-06-15 16:26 ` Kyle Jones
1999-06-15 16:33 ` Hamish Macdonald
1999-06-15 17:57 ` Kyle Jones
1999-07-03 9:28 ` Lars Magne Ingebrigtsen
1999-07-03 12:40 ` Hrvoje Niksic
1999-07-04 4:42 ` Lars Magne Ingebrigtsen
1999-06-15 17:24 ` Jan Vroonhof
1999-06-15 17:30 ` William M. Perry
1999-06-15 17:43 ` Jan Vroonhof
1999-06-15 18:05 ` William M. Perry
1999-06-15 18:52 ` Jan Vroonhof
1999-06-15 15:00 ` Lee Willis
1999-06-15 18:56 XEmacs Patches Moderator Robot
1999-06-15 19:04 ` Jan Vroonhof
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=6w674pa2mg.fsf@lucent.com \
--to=hamishm@lucent.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).