Hello, I have now tried this in the latest snapshot and now it works.
Bengt Larsson wrote:
>I seem to have a problem with wildcards from the Windows command line
>when there are high-bit characters in a filename.
>
>A directory contains only the two files "user" and "användare"
>("användare" being
On Dec 30 17:42, Christopher Faylor wrote:
> On Wed, Dec 30, 2009 at 01:30:19PM -0500, Christopher Faylor wrote:
> >On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
> >>I seem to have a problem with wildcards from the Windows command line
> >>when there are high-bit characters in a fi
On Wed, Dec 30, 2009 at 01:30:19PM -0500, Christopher Faylor wrote:
>On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
>>I seem to have a problem with wildcards from the Windows command line
>>when there are high-bit characters in a filename.
>>
>>A directory contains only the two file
On Wed, Dec 30, 2009 at 08:17:21PM +0100, Bengt Larsson wrote:
>Dave Korn wrote:
>>Bengt Larsson wrote:
>>
>>> Every port of Unix utilities to Windows such as ls, grep and so forth do
>>> this globbing internally.
>>
>> No. Not "every port". Specifically, not Cygwin ones: they get it done for
>>
Christopher Faylor wrote:
>On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
>>I seem to have a problem with wildcards from the Windows command line
>>when there are high-bit characters in a filename.
>>
>>A directory contains only the two files "user" and "anv?ndare"
>>("anv?ndare" be
Dave Korn wrote:
>Bengt Larsson wrote:
>
>> Every port of Unix utilities to Windows such as ls, grep and so forth do
>> this globbing internally.
>
> No. Not "every port". Specifically, not Cygwin ones: they get it done for
>them, by the shell that launches them, or in fallback cases by the Cygw
Bengt Larsson wrote:
> Every port of Unix utilities to Windows such as ls, grep and so forth do
> this globbing internally.
No. Not "every port". Specifically, not Cygwin ones: they get it done for
them, by the shell that launches them, or in fallback cases by the Cygwin DLL.
They don't ha
On 12/30/2009 11:33 AM, Bengt Larsson wrote:
It doesn't work for echo because "echo" is a builtin in the Windows
shell.
Okay, imatwit, of course it is. One bug, then. :)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Warren Young wrote:
>On 12/30/2009 11:16 AM, Larry Hall (Cygwin) wrote:
>> On 12/30/2009 01:08 PM, Warren Young wrote:
>>> Another thing that doesn't work:
>>>
>>> c:\> echo W*
>>
>> Ah, right. So my idea doesn't make sense. Never mind. ;-)
>
>I think we're looking at two bugs, though. The origina
On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
>I seem to have a problem with wildcards from the Windows command line
>when there are high-bit characters in a filename.
>
>A directory contains only the two files "user" and "anv?ndare"
>("anv?ndare" being user in Swedish):
>
> C:\Do
Warren Young wrote:
>On 12/30/2009 10:18 AM, Bengt Larsson wrote:
>>> Try "noglob" if your shell is not Cygwin-aware.
>>
>> Eh? The problem is that it doesn't glob when it should. The shell is
>> standard CMD.EXE, ie Windows console.
>
>The behavior you're relying on is a nonstandard Cygwin extens
On 12/30/2009 11:16 AM, Larry Hall (Cygwin) wrote:
On 12/30/2009 01:08 PM, Warren Young wrote:
Another thing that doesn't work:
c:\> echo W*
Ah, right. So my idea doesn't make sense. Never mind. ;-)
I think we're looking at two bugs, though. The original post appears to
be about a Unicode
On 12/30/2009 01:08 PM, Warren Young wrote:
Another thing that doesn't work:
c:\> echo W*
Ah, right. So my idea doesn't make sense. Never mind. ;-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalt
On Wed, Dec 30, 2009 at 06:20:32PM +, Dave Korn wrote:
>Hang on though, isn't there some code in the cygwin dll to do globbing
>for just this situation, when you want to launch a cygwin executable
>from a non-cygwin context?
Yes.
cgf
--
Problem reports: http://cygwin.com/problems.html
On 12/30/2009 01:20 PM, Dave Korn wrote:
Thorsten Kampe wrote:
* Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)
Try "noglob" if your shell is not Cygwin-aware.
Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.
The shell (Cmd) does the
On 12/30/2009 10:18 AM, Bengt Larsson wrote:
Try "noglob" if your shell is not Cygwin-aware.
Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.
The behavior you're relying on is a nonstandard Cygwin extension which
most Cygwin users, I
Thorsten Kampe wrote:
> * Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)
>>> Try "noglob" if your shell is not Cygwin-aware.
>> Eh? The problem is that it doesn't glob when it should. The shell is
>> standard CMD.EXE, ie Windows console.
>
> The shell (Cmd) does the globbing. Describe your proble
* Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)
> >Try "noglob" if your shell is not Cygwin-aware.
>
> Eh? The problem is that it doesn't glob when it should. The shell is
> standard CMD.EXE, ie Windows console.
The shell (Cmd) does the globbing. Describe your problem in a Microsoft
newsgroup.
>Try "noglob" if your shell is not Cygwin-aware.
Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.
On 12/30/2009 11:36 AM, Bengt Larsson wrote:
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.
A directory contains only the two files "user" and "användare"
("användare" being user in Swedish):
C:\Documents and Settings\B
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.
A directory contains only the two files "user" and "användare"
("användare" being user in Swedish):
C:\Documents and Settings\Bengt2\Desktop\test\ttt>ls -l
total 0
-rw-r--
21 matches
Mail list logo
