From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Bug in command-line globbing Date: 13 Dec 2002 17:53:48 GMT Organization: Aachen University of Technology (RWTH) Lines: 30 Message-ID: References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1039802028 8880 137.226.32.75 (13 Dec 2002 17:53:48 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 13 Dec 2002 17:53:48 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Arthur J. O'Dwyer wrote: > True. On the other hand, DJGPP behaves like Unix programs: they > generally perform filename globbing. As a matter of fact, Unix programs generally *don't* do filename globbing. The command line shell does it for them. DOS' default shell, command.com, doesn't. Which is where this whole problem really began: DJGPP wants to be as compatible to Unix as possible, so it has to do the globbing command.com has failed to. > Wht do you mean, "Some cases of mismatched quotes are actually the > shell's fault"? In some particular cases, command.com _will_ expand/modify some of your quoted command line input, and fail miserably. Just as one gets used to expecting whenever MS tries to follow in the steps of Unix traditions. IIRC, your "backslash as the last letter of a double-quoted string" is exactly one such case. > What I really want is to design a 'tr'-like program which takes as > arguments a list of hyphen-options, followed by one or two regexes, > followed optionally by a (list of) filename(s). So turn *off* all the globbing, as explained to you in the FAQ, and in earlier replies in this thread. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.