Re: Possible bug in TRAMP?
Sun, 20 Mar 2005 17:59:51 +0000, Andrew Nesbit wrote:
On 20 Mar 2005, at 17:45, Adrian Aichner wrote:
> Adrian Aichner <adrian(a)xemacs.org> writes:
>
>> Andrew Nesbit <andrew(a)siru.org> writes:
>>
>>> itimer "with-timeout<5>" signaled: (void-function
>>> with-timeout-handler)
>
> There are some known itimer infidelities.
[snip]
> This look like it:
> http://list-archive.xemacs.org/cgi-bin/wilma_hiliter/xemacs-beta/
> 200409/msg00374.html
OK, thanks for pointing that out. So it seems it's a bug in some
uudecode/uuencode tool on the remote Mac OS X.
I'm using the workaround for this:
,----[ init.el ]
| (defvar tramp-coding-commands
| '(("mimencode-bad -b" "mimencode-bad -u -b"
| base64-encode-region base64-decode-region)
| ("mmencode-bad -b" "mmencode-bad -u -b"
| base64-encode-region base64-decode-region)
| ("recode data..base64" "recode base64..data"
| base64-encode-region base64-decode-region)
| ("uuencode-bad xxx" "uudecode-bad -o -"
| tramp-uuencode-region uudecode-decode-region)
| ("uuencode-bad xxx" "uudecode-bad -p"
| tramp-uuencode-region uudecode-decode-region)
| ("uuencode-bad xxx" "tramp_uudecode"
| tramp-uuencode-region uudecode-decode-region)
| ("tramp_encode_with_module" "tramp_decode_with_module"
| base64-encode-region base64-decode-region)
| ("tramp_encode" "tramp_decode"
| base64-encode-region base64-decode-region)))
`----
This is only a hack.
--
Regards,
Andrey.