From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg) Newsgroups: comp.os.msdos.djgpp Subject: Re: GNU Pascal (gpc) 2.1 released Date: 24 May 2002 12:28:42 GMT Organization: Ericsson Erisoft AB, Sweden Lines: 23 Message-ID: References: <3CED528D DOT 7DCF9660 AT yahoo DOT com> <3CED6BA6 DOT 48D4D0FE AT phekda DOT freeserve DOT co DOT uk> <7458-Fri24May2002135355+0300-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: lws256.lu.erisoft.se X-Newsreader: TIN [version 1.2 PL2] To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote: : > : bash-2.04$ ls -l foo : > : c:/djgpp/bin/ls: foo: No such file or directory (ENOENT) : > : bash-2.04$ rm -fv @foo : > Is there any good reason why a non-existent file shouldn't produce a : > warning? : To avoid an annoying warning in case @foo is not a response file at : all, but a legit command-line argument? Ok. But in the case of rm there isn't a legit command-line argument starting with @, is there? Assuming rm is part of fileutils (can't check that right now) and assuming this @ feature is common to all fileutils program (should be IIRC), which of the fileutils program would have a legit command-line argument starting with @? This question is somewhat retorical, because when my WINDOZE system works again, I'll examine the situation. Right, MartinS