Subject: > "complete.el" on WindowsNT 4.0

From: David Biesack <[email-masked]>
Date: Fri, 30 May 1997 09:10:34 -0400

>  Hans> Is there a way to get the package "complete.el" to work on
>  Hans> WindowsNT 4.0 just as cool as it does under UNIX ??
> 
> The problem seems to be that the function `PC-expand-many-files' calls
> 
>   (shell-command (concat "echo " name) t)
> 
> to get the names of the files all on a single line, relying on Unix-style
> shell expansion. If you could find a utility that does that, then all
> would be well -- more or less. 
> 
>                         Peter

If you have bash installed, you can use

(shell-command (concat "bash -c \"echo " name "\"") t)

---

From: Peter Breton <[email-masked]>
Date: Fri, 30 May 1997 10:34:30 -0400

>> to get the names of the files all on a single line, relying on
 >> Unix-style shell expansion. If you could find a utility that does
 >> that, then all would be well -- more or less.
 >> 
 >> Peter

 David> If you have bash installed, you can use

 David> (shell-command (concat "bash -c \"echo " name "\"") t)

You will have to modify complete.el to do so, though. I think the "right"
modification would be to change the name parsing algorithm to handle
files with embedded spaces. Less good, but still an improvement, would be 
to change the above line to something like

  (shell-command (concat PC-echo-command " " name) t)

and then add:

(defvar PC-echo-command "echo" 
"Shell command to perform wildcard expansion.")

Then you could use MKS echo, bash, etc

			Peter

---

From: Peter Breton <[email-masked]>
Date: Thu, 29 May 1997 18:49:33 -0400

Hans> Whatever I tried so far does not seem to have any effect at
 Hans> all.

 Hans> ("complete.el" allows wildcards when retrieving files in
 Hans> directories/filenames)

to get the names of the files all on a single line, relying on Unix-style
shell expansion. If you could find a utility that does that, then all
would be well -- more or less. This scheme probably won't work with
filenames with embedded spaces, which are rare on Unix but common on
95 and NT. One filename per line would be much better, and could use
"ls" or the equivalent.

			Peter