CLI based code has space separator. Always has done. Probably always will. On windows long file names with spaces are enclosed in double quotes. In fact if you want to pass a string with spaces as a parameter to any program, putting it inside "double quotes" will work.
In cygwin, I have to escape the space to use it. Both mechanisms are valid, but obviously incompatible. E.g. On Windows C: CD "\Program Files\Zend" Will take me to ... C:\Program Files\Zend As expected. In my Cygwin installation I tried ... cd /cygdrive/c cd Program\ Files/Zend And this worked ... /cygdrive/c/Program Files/Zend If all the paths in the .in (or the environment variables which contain paths/files/etc) are passed through sed, then this should be OK? The further issue is what happens to filenames with spaces in. I don't think these are used. -----Original Message----- From: gerzson [mailto:[EMAIL PROTECTED] Sent: 18 November 2005 08:50 To: Gabor Hojtsy Cc: [EMAIL PROTECTED]; PHP Docs List Subject: Re: [PHP-DOC] PHP Doc ./configure > 1. It is really a bad idea to put command line programs into a folder > with space in the name (or any special character for that matter) BTW, IMHO it's a "really bad idea" in 2005 not to let the user choose where to install his own programs. I repeat "In 2005..." -- Papp, Gyozo
