Re: Fails to launch batch script in some directories

On Apr 23 11:20, Brian Inglis wrote:
> On 2018-04-23 02:44, Corinna Vinschen wrote:
> > On Apr 23 08:43, David Macek wrote:
> >> On 21. 4. 2018 17:38, Brian Inglis wrote:
> >>> See my other post in this thread where strace shows @ handling is not involved,
> >>> as the script directory and name are normalized and converted to a win32 path
> >>> correctly, but child_info_spawn::worker does not appear to quote args with
> >>> spaces (or apostrophes) when building the command line, despite the comment near
> >>> the top of the function.
> >> Do you have a test case for this? In my testing, paths with spaces (like
> >> 'x y' instead of '@ x') work just fine.
> > Brian has a point though. It's not a space *in* a filename, it's a
> > *trailing* space. And that points to the cause of the problem:
>
> No trailing space - middle char - the directory name was exactly as in the OP:
> ".../@ x/" - see strace output.
My bad. When I read the OP I read "@ " as dir name. I missed the "x".
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat