Mail Archives: djgpp/1997/05/28/08:05:54
From: | mdruiter AT cs DOT vu DOT nl (Ruiter de M)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | (Another) BASH-bug? Or feature?
|
Date: | 28 May 1997 11:19:40 GMT
|
Organization: | Fac. Wiskunde & Informatica, VU, Amsterdam
|
Message-ID: | <5mh4cc$qcp@star.cs.vu.nl>
|
NNTP-Posting-Host: | sloep102.cs.vu.nl
|
Lines: | 22
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I have noticed the following behaviour of the latest BASH-port version:
bash$ ls */PLUGIN/OPT
ls: No such file or directory */PLUGIN/OPT (ENOENT) (or alike)
bash$ ls */plugin/opt
rx/plugin/opt
I run DOS7.0 WITHOUT Win95 (so no LFN either), with LFN=n in DJGPP.ENV.
Is this behaviour the way it _should_ be, or is there something wrong
(or just not right yet) in the use of regexps in BASH?
I noticed earlier, that BASH doesn't like the DJGPP '...'-syntax
either, probably because it uses another regexp-parser? This is fine
with me, but caps in filenames are something DOS should ignore right?
I hope someone understands what I am saying :)
--
Groeten, Michel. http://www.cs.vu.nl/~mdruiter
\----/==\----/
\ / \ / "Als je voetbalcriminaliteit wilt tegengaan,
\/ \/ moet je ophouden met voetballen", Nordholt.
- Raw text -