Re: UUdecode and NTemacs

[Andrew Innes <andrewi@harlequin.co.uk>]

On Fri, 4 Apr 1997 10:59:10 +0200 (MET DST), Fabrice POPINEAU <popineau@esemetz.ese-metz.fr> said:
>Hi,
>
>The following code  in gnus-uu.el (5.4.36)  needs some modification to
>work under NTemacs:
>
>	  ;; Start a new uudecoding process.
>	  (let ((cdir default-directory))
>	    (unwind-protect
>		(progn
>		  (cd gnus-uu-work-dir)
>		  (setq gnus-uu-uudecode-process
>			(start-process
>			 "*uudecode*"
>			 (get-buffer-create gnus-uu-output-buffer-name)
>;			 shell-file-name shell-command-switch
>;			 (format "cd %s %s uudecode" gnus-uu-work-dir
>;				 gnus-shell-command-separator))))
>			 "uudecode")))
>	      (cd cdir)))
>
>There are 2 problems:
>
>- gnus-uu-work-dir is "f:/tmp/gnusa00195" and if your shell is "cmd",
>it can't 'cd' to some path with '/', it needs '\'

You can solve this by binding directory-sep-char to '\' while calling
expand-file-name; this will give the correct format on Windows 95/NT.

>- anyway, I'm not sure NTemacs can accept "cd f:\\tmp\\gnusa00195 &&
>uudecode" as a program to start.

If you are "on" drive F at the time, then this will work on Windows NT.
It won't work on Windows 95, using the standard shell.

>As there was a (cd gnus-uu-work-dir) just before, is it useful to keep
>the "cd tmpdir &&" into the starting process ?

It should be a no-op, I think.  If the original code above works without
that, then you have your solution.

AndrewI

-- 
Andrew Innes                    Software Developer, Electronic Publishing
Harlequin Limited, Longstanton House, Longstanton, Cambridge CB4 5BU, U.K.
Tel: +44 1954 785468  Fax: +44 1954 785444  WWW: http://www.harlequin.com