From xemacs-m  Mon Jan 27 20:08:42 1997
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.31])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id UAA21112 for <xemacs-beta@xemacs.org>; Mon, 27 Jan 1997 20:08:41 -0600 (CST)
Received: from sandman (sandman.cisco.com [171.68.209.51]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id SAA11364 for <xemacs-beta@xemacs.org>; Mon, 27 Jan 1997 18:08:12 -0800 (PST)
Received: (from drich@localhost) by sandman (SMI-8.6/8.6.12) id SAA05179; Mon, 27 Jan 1997 18:08:11 -0800
Date: Mon, 27 Jan 1997 18:08:11 -0800
Message-Id: <199701280208.SAA05179@sandman>
From: Dan Rich <drich@cisco.com>
To: xemacs-beta@xemacs.org
Subject: Continued jka-compr problems 
Reply-To: drich@cisco.com
X-Face: >>@YIrj6h(9FH@Qs_-ob2y~:HhB3<K:s^%ne_GjM`oNo3yFzbT'Kover1p6Qf|2_'8inv!W
 x^4ApmkH}yJ*clwm{;w(]]EV=YexeKB[\$G>j#fE)'04Kv^h\Yc+PG%t~'xXevX509R
X-Planation: X-Face can be viewed with "faces" or "xmail" (X11R5 contrib tape).
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII

It looks like the patch I sent earlier doesn't quite fix the problem
(which will teach me to send in a patch before I have fully tested it).

Now, when I attempt to save a gziped file, I'm getting an error, and
with debug-on-error set to 't, I get the following stack trace:

Signaling: (wrong-type-argument stringp #<coding_system iso-2022-8-unix>)
  write-region-internal(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/tmp/jka-comaea000HX#" t dont #<coding_system iso-2022-8-unix> #<coding_system iso-2022-8-unix>)
  ange-ftp-real-write-region(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/tmp/jka-comaea000HX#" t dont #<coding_system iso-2022-8-unix> nil)
  write-region(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/tmp/jka-comaea000HX#" t dont #<coding_system iso-2022-8-unix> nil)
  apply(write-region (#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/tmp/jka-comaea000HX#" t dont #<coding_system iso-2022-8-unix> nil))
  jka-compr-run-real-handler(write-region (#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/tmp/jka-comaea000HX#" t dont #<coding_system iso-2022-8-unix> nil))
  jka-compr-write-region(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet #<coding_system iso-2022-8-unix>)
  apply(jka-compr-write-region (#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet #<coding_system iso-2022-8-unix>))
  jka-compr-handler(write-region #<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet #<coding_system iso-2022-8-unix>)
  write-region-internal(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet nil #<coding_system iso-2022-8-unix>)
  ange-ftp-real-write-region(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet nil nil)
  write-region(#<marker at 2103609 in INBOX> #<marker at 2108229 in INBOX> "/home/drich/Mail/cisco-cco.gz" t quiet)

The part of this I don't understand is that when write-region-internal
calls jka-compr-handler the first time it is eating the lockname
argument (nil), which is causing the rest of the calls to get rather
strange (lockname != coding-system).  Does anyone know why this might
be happening?  I'm assuming jka-compr-handler is being called because
of the settings in file-name-handler-alist, but I don't see what could
be eating the argument.

-- 
Dan Rich <drich@cisco.com>  |	http://www.employees.org/~drich/
Senior Webmaster            | "Danger, you haven't seen the last of me!" 
Cisco Systems, Inc.         |   "No, but the first of you turns my stomach!"
(408) 527-3195              |           -- The Firesign Theatre's Nick Danger

       Friends of Randal Schwartz: http://www.lightlink.com/fors/

