Am 25.09.2016 um 13:11 schrieb David Stacey:
On 25/09/16 12:00, Bengt Larsson wrote:
C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö
åäö
C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö"
"åäö"
(the quote marks are left in)
C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l
total 1
-rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt
-rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions
-rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt
C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt
ls: cannot access '*.txt': No such file or directory
It looks as if you're using a Windows command prompt rather than Bash.
Both 'problems' are actually a feature of the command prompt. Try
again from a Bash shell.
He's talking about an interworking issue between Windows cmd and cygwin
(which isn't completely out of scope of cygwin);
and in fact, there has been a recent change, look for the mail thread
"pass arguments enclosed with double quotes from bash shell to windows
program".
In fact, with two files, one of them containing non-ASCII characters,
like ab.txt and äö.txt, the simplified test case
C:\whatever>echo *.txt
displays this with cygwin 2.5.2:
ab.txt äö.txt
and this with cygwin 2.6.0:
*.txt
Considering that the change, as I remember, was a quite successful
workaround for problems with quote marks, it may be considered a
trade-off with changed bias, rather than a bug, however :)
------
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
