Hamish Macdonald <hamishm(a)lucent.com&gt; writes: > >>>>> On 15 Jun 1999 11:34:06 -0400, > >>>>> In message <6wemjd32c1.fsf(a)lucent.com&gt;, > >>>>> 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. this is because of the #!%!＠＠!#%!＠#%＠!＠ing format-alist crap that automatically inlines images. This code is bogus and people have been begging for it to be removed on the beta list for a while. :) If you set format-alist to nil you should be ok.