X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: disable bash builtin(s) Date: 25 Jan 2002 18:31:21 GMT Organization: Aachen University of Technology (RWTH) Lines: 26 Message-ID: References: <20020123124043 DOT A17742 AT kendall DOT sfbr DOT org> <20020124114332 DOT B10567 AT kendall DOT sfbr DOT org> <20020125112457 DOT A1110 AT kendall DOT sfbr DOT org> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1011983481 11670 137.226.32.75 (25 Jan 2002 18:31:21 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 25 Jan 2002 18:31:21 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com JT Williams wrote: > -: The only way this can ever trouble the user would be if some program > -: was installed under the name 'select' --- which is quite obviously a > -: rather bad idea, for exactly this reason. [...] > The conflict with `select' has a similar origin; `select' is a standard > database operation, but it conflicts with a bash keyword. Why not use "SELECT" instead of "select" as the name of the DB operation of that name? SQL is usually written in all-caps, in my experience. So typing "SELECT" should feel natural enough for users. Bash won't mix that up with 'select', but DOS will, i.e. even if the program is called 'select.exe', I think it'll still be found by DJGPP bash if you type SELECT. Or just bite the bullet and use a prefix command or alias. Something like alias sel c:/some/where/select.exe -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.