From xemacs-m  Tue Feb  4 10:14:43 1997
Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA05399
	for <xemacs-beta@xemacs.org>; Tue, 4 Feb 1997 10:14:42 -0600 (CST)
Received: from mr2.exu.ericsson.se (mr2.exu.ericsson.com [138.85.147.12]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id KAA07038 for <xemacs-beta@xemacs.org>; Tue, 4 Feb 1997 10:14:12 -0600 (CST)
Received: from screamer.rtp.ericsson.se (screamer.rtp.ericsson.se [147.117.133.13]) by mr2.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with SMTP id KAA11234 for <xemacs-beta@xemacs.org>; Tue, 4 Feb 1997 10:14:11 -0600 (CST)
Received: from rcur (rcur18.rtp.ericsson.se [147.117.133.138]) by screamer.rtp.ericsson.se (8.6.12/8.6.4) with ESMTP id LAA03538 for <xemacs-beta@xemacs.org>; Tue, 4 Feb 1997 11:14:09 -0500
To: XEmacs Mailing List <xemacs-beta@xemacs.org>
Subject: 20.0 bug in tm
Mime-Version: 1.0 (generated by tm-edit 7.101)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 04 Feb 1997 11:14:08 -0500
Message-ID: <20834.855072848@rtp.ericsson.se>
From: Raymond Toy <toy@rtp.ericsson.se>


Compiled 20.0 from a full distribution on Solaris 2.5.  Full build
went just fine.  However, I have the following bug.

In mh-e, when I try to include a file via C-c C-x C-i <some file> with
7bit transfer encoding, I get the following error and lisp traceback:

Signaling: (invalid-function (macro . #<compiled-function (from "emu-x20.elc") (&rest body) "...(9)" [let ((file-coding-system-for-read (quote no-conversion))) body] 3>))
  as-binary-input-file(("/home/unix/toy/.bashrc" 2902))
  insert-binary-file-contents-literally("~/.bashrc")
  mime-insert-encoded-file("~/.bashrc" "7bit")
  mime-editor/insert-binary-file("~/.bashrc" "7bit")
  mime-editor/insert-file("~/.bashrc" nil)
  call-interactively(mime-editor/insert-file)

This also happens if I use 8bit transfer encoding, but does not happen
with any other transfer encoding.

However, if I load emu.el and evaluate the defun for
insert-binary-file-contents-literally, I no longer get this error
message.  Perhaps this means the files were compiled in the wrong
order and the wrong as-binary-input-file has been used for this
function?  

Ray

