X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f Date: Thu, 24 Jan 2002 11:43:32 -0600 From: JT Williams To: djgpp AT delorie DOT com Cc: Eli Zaretskii Subject: Re: disable bash builtin(s) Message-ID: <20020124114332.B10567@kendall.sfbr.org> Mail-Followup-To: djgpp AT delorie DOT com, Eli Zaretskii References: <20020123124043 DOT A17742 AT kendall DOT sfbr DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from eliz@is.elta.co.il on Thu, Jan 24, 2002 at 09:18:06AM +0200 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk -: > Can I selectively disable bash builtin commands? -: -: According to the Bash manual, there's a special command to do that: -: "enable -n". My initial message was misworded; sorry about that. I knew about the enable command; what I was looking for is a way to disable a bash *keyword* (not a builtin). The only way I know to do this is to quote the keyword, e.g., type "select" or 'select' (with quotes) or even \select (with backslash) to force a path search for a `select' program or script. Hackers can live with this, even take a perverse delight in it, but Joe L User isn't known for tolerating such quirks. I suppose I could build a custom bash for this particular application....