From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 18745@debbugs.gnu.org
Subject: bug#18745:
Date: Wed, 28 Oct 2015 18:01:48 +0200 [thread overview]
Message-ID: <83twpb2d8z.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SREX+S4+FifBDejDBb8G8nTAntRgbh4aJeca8Vcf7Tzqg@mail.gmail.com>
> 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).
next prev parent reply other threads:[~2015-10-28 16:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 4:33 bug#18745: 24.3; MS Windows, `call-process-shell-command' fails on `shell-quote-argument'ed bat file with quoted args Noam Postavsky
2014-10-16 6:50 ` Eli Zaretskii
2014-10-16 13:47 ` Stefan Monnier
2014-10-16 13:57 ` Eli Zaretskii
2014-10-16 16:28 ` Noam Postavsky
2014-10-16 17:06 ` Eli Zaretskii
2014-10-16 21:30 ` Noam Postavsky
2014-10-22 1:12 ` Noam Postavsky
2014-10-22 17:12 ` Eli Zaretskii
2014-10-23 1:33 ` Noam Postavsky
2014-10-23 15:52 ` Eli Zaretskii
2014-10-25 9:16 ` Eli Zaretskii
2014-10-25 14:03 ` Noam Postavsky
2014-10-16 20:15 ` Stefan Monnier
2014-10-16 21:50 ` Noam Postavsky
2014-10-17 0:38 ` Stefan Monnier
2014-10-17 6:10 ` Eli Zaretskii
2014-10-17 6:05 ` Eli Zaretskii
2015-10-27 11:49 ` bug#18745: Juanma Barranquero
2015-10-27 19:14 ` bug#18745: Eli Zaretskii
2015-10-27 23:24 ` bug#18745: Juanma Barranquero
2015-10-28 16:01 ` Eli Zaretskii [this message]
2015-10-29 3:38 ` bug#18745: Juanma Barranquero
2015-10-29 16:17 ` bug#18745: Eli Zaretskii
2015-10-29 17:22 ` bug#18745: Juanma Barranquero
2015-10-30 14:25 ` bug#18745: Juanma Barranquero
2015-10-30 14:55 ` bug#18745: Eli Zaretskii
2015-10-30 17:09 ` bug#18745: Juanma Barranquero
2015-10-30 20:10 ` bug#18745: Eli Zaretskii
2015-10-31 23:20 ` bug#18745: Juanma Barranquero
2015-11-01 17:49 ` bug#18745: Eli Zaretskii
2015-11-01 18:29 ` bug#18745: Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83twpb2d8z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18745@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.