[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18745:
From: |
Eli Zaretskii |
Subject: |
bug#18745: |
Date: |
Wed, 28 Oct 2015 18:01:48 +0200 |
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 28 Oct 2015 00:24:29 +0100
> Cc: 18745@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).
- bug#18745:, Juanma Barranquero, 2015/10/27
- bug#18745:, Eli Zaretskii, 2015/10/27
- bug#18745:, Juanma Barranquero, 2015/10/27
- bug#18745:,
Eli Zaretskii <=
- bug#18745:, Juanma Barranquero, 2015/10/28
- bug#18745:, Eli Zaretskii, 2015/10/29
- bug#18745:, Juanma Barranquero, 2015/10/29
- bug#18745:, Juanma Barranquero, 2015/10/30
- bug#18745:, Eli Zaretskii, 2015/10/30
- bug#18745:, Juanma Barranquero, 2015/10/30
- bug#18745:, Eli Zaretskii, 2015/10/30
- bug#18745:, Juanma Barranquero, 2015/10/31