Re: REPOST: XEmacs MULE incompatiblity w/ GnuPG files?

Hi Glynn, thanks for the suggestions... GC> Presumably it's a file-coding problem, i.e. it still occurs if GC> you use --with-file-coding instead of --with-mule. GC> If so, whichever "auto-decode" package is involved (mailcrypt, GC> jka-compr, ...) should probably bind coding-system-for-read GC> and/or coding-system-for-write to 'binary. GC> Also, it can usually be worked around by the user by setting GC> process-coding-system-alist, e.g. GC> (push '("/.*" . binary) process-coding-system-alist) My XEmacs-fu is bit rusty, and I'm not familar at all with the coding system stuff, but I think we have a problem here. I'm using crypt.el via crypt-find-file-hook in my find-file-hook to do the auto decrypting. By the time crypt-find-file-hook gets into the act, the file's already read into the buffer isn't it? So it's too late to bind coding-system-for-read to catch this. I also tried setting process-coding-system-alist as described, but that didn't seem to do the trick either. Presumably the car is supposed to match a program name, and I'm not sure if it's invoking gpg via absolute path or relative path, so I tried this: (push '(".*gpg" . binary) process-coding-system-alist) This resulting in a different error: gpg: packet with S2K 3 too short Fun. ;) -Barry