Re: Help test EFS
Jay Levitt writes:
Since this is getting pretty ugly, an alternative is to stick with
telling users to customise efs-ftp-program-name to point to the version
of ftp.exe that ships with Windows.
Can XEmacs elisp access Windows environment variables? If so, this should
always be available at %SystemRoot%\system32\ftp.exe, at least on NT/2000
boxes.
c:\WINDOWS\FTP.EXE on w98.
I have a vague worry that using windows ftp.exe will be swapping
one set of problems for another...
-jeff
----- Original Message -----
From: "Jonathan Harris" <jhar(a)tardis.ed.ac.uk>
Sent: Monday, May 21, 2001 8:41 PM
> Jerker Haglund wrote:
>
> > put c:\myweb\behag\anmlan.htm /html/behag/anmlan.htm
> > /usr/bin/ftp: local: c:mywebbehaganmlan.htm: No such file or directory
>
> The fix to efs-tmp-name-template in efs release 1.20pre1 / package 1.25
> is insufficient since it isn't just temporary file names that get passed
> to the ftp program, as the above example shows. A hack like the
> following is also required.
>
> (defun efs-maybe-quote-local-path (path)
> "Quote special characters in PATH if `efs-quote-local-paths' is
> non-nil."
> + (if (eq system-type 'windows-nt)
> + (setq path (replace-in-string path "\\\\" "/")))
> (if efs-quote-local-paths
> (apply (function concat)
> (mapcar (function
>
>
Since this is getting pretty ugly, an alternative is to stick with
telling users to customise efs-ftp-program-name to point to the version
of ftp.exe that ships with Windows.