GNU bug report logs - #18745
24.3; MS Windows, `call-process-shell-command' fails on `shell-quote-argument'ed bat file with quoted args

Previous Next

Package: emacs;

Reported by: Noam Postavsky <npostavs <at> users.sourceforge.net>

Date: Thu, 16 Oct 2014 04:35:01 UTC

Severity: minor

Found in versions 25.0.50, 24.3

Done: Juanma Barranquero <lekktu <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 18745 <at> debbugs.gnu.org
Subject: bug#18745: 
Date: Wed, 28 Oct 2015 18:01:48 +0200
> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Wed, 28 Oct 2015 00:24:29 +0100
> Cc: 18745 <at> debbugs.gnu.org
> 
> > Do you see the same result if you invoke 'echo' from the cmd prompt?
> > IOW, does this mean Windows 10 changed the behavior of the built-in
> > 'echo', and it now removes trailing whitespace from its argument?
> 
> IIUC your question, no
> 
> C:\Users\Juanma>echo A>A.txt
> 
> C:\Users\Juanma>echo B >B.txt
> 
> C:\Users\Juanma>dir *.txt
> 
> 28/10/2015 00:23 3 A.txt
> 28/10/2015 00:23 7 B.txt
> 2 archivos 10 bytes

The test actually uses a batch file, so I think it's worthwhile to try
that, and see if the behavior of 'echo' when called from a batch file
changed.

If not, then please try digging deeper, because the unmodified test
work OK for me (not on Windows 10).




This bug report was last modified 9 years and 208 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.