Kai,
At 14:53 (GMT+0200) on 17-September-2002, Kai Gro�johann wrote: > Douglas Gray Stephens <[EMAIL PROTECTED]> writes: > > > Thanks. VM can use the uuencode.exe that comes with the GNU share > > file of Unix binaries for Windows, and so is quicker than lisp. I > > recall that VM can default to a lisp version for base64 and uuencode, > > but obviously this is not as fast. > > Okay, I see that I should add support for that to tramp-uu.el. But > as it is an optimization only... > > Wait a second. Tramp tries to run uuencode, too. See > tramp-coding-commands. So you're saying that Tramp didn't run > uuencode in the right way? No, when I set the tramp-coding-commands as you asked, tramp ran uuencode prior to base64. > How do you run that uuencode under Windows so that it reads standard > input and writes standard output? VM uses uuencode to read from STDIN, but writes to the file specified in the stream: vm-mime-uuencode-decoder-program's value is "uudecode" Documentation: *Non-nil value should be a string that names UUENCODE decoder. If the program is in your executable search path, you need not specify a full pathname. The program should expect to read uuencoded data on its standard input and write the converted data to the file specified in the ``begin'' line at the start of the data. You can customize this variable. Defined in `vm'. I guess if one has perl on the Windows box, then one could easily handle a STDIN/STDOUT uudecode in a faster manner than via lisp. Douglas. -- ================================ Douglas GRAY STEPHENS Technical Architect (Directories) Schlumberger Cambridge Research High Cross, Madingley Road, Cambridge. CB3 0EL ENGLAND Phone +44 1223 325295 Mobile +44 773 0051628 Fax +44 1223 311830 Email [EMAIL PROTECTED] ================================ _______________________________________________ Tramp-devel mailing list [EMAIL PROTECTED] http://mail.freesoftware.fsf.org/mailman/listinfo/tramp-devel
