On 10/04/2006, Andy Telford wrote:
I guess the current bash doesn't jive with cygwin 1.5.19(0.150/4/2)
2006-01-16 15:01 i686 Cygwin,
Yes, I'm quite sure bash doesn't speak jive. ;-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 89
On 04 October 2006 18:41, Andy Telford wrote:
> Eureka! I checked the cygcheck output and noticed that my cygwin dll was
> old even though "setup" thought I was up to date. Maybe a previous cygwin
> update failed to complete properly? I reinstalled the base cygwin package
> using setup and now
rrent bash doesn't jive with cygwin 1.5.19(0.150/4/2) 2006-01-16
15:01 i686 Cygwin,
Thanks everyone,
Andrew
- Original Message
From: Dave Korn <[EMAIL PROTECTED]>
To: cygwin mailing list
Sent: Wednesday, October 4, 2006 1:13:22 PM
Subject: RE: bash shell globbing not w
On 04 October 2006 18:08, Andy Telford wrote:
> Nope. The directory was not empty, so * should have been expanded by the
> shell according to the bash "pathname expansion" rules. I included the
> SHELLOPTS variable in the first email to show that noglob is not set.
>
> $ mkdir newdir
> $ cd ne
Nope. The directory was not empty, so * should have been expanded by the shell
according to the bash "pathname expansion" rules. I included the SHELLOPTS
variable in the first email to show that noglob is not set.
$ mkdir newdir
$ cd newdir
$ touch newfile
$ ls
newfile
$ ls *
ls: *: No such fil
On 04 October 2006 16:47, Andy Telford wrote:
> Has any experienced this?
>
> - "ls" works but "ls *" returns "ls: *: No such file or directory"
> - same if I just use the shell builtin "echo *" just returns "*"
You are in an empty directory. There is nothing for the '*' to match.
As glob
Andy Telford wrote:
> Has any experienced this?
>
> - "ls" works but "ls *" returns "ls: *: No such file or directory"
> - same if I just use the shell builtin "echo *" just returns "*"
I experience this every time when I issue those commands with an empty
directory as cwd. That's simply the way
7 matches
Mail list logo
