From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20093 invoked from network); 11 Oct 1999 08:20:56 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Oct 1999 08:20:56 -0000 Received: (qmail 8194 invoked by alias); 11 Oct 1999 08:20:50 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8200 Received: (qmail 8187 invoked from network); 11 Oct 1999 08:20:50 -0000 Subject: Re: PATCH: Re: PATCH: emulate (Re: Prompt fun) In-Reply-To: <991010231931.ZM5336@candle.brasslantern.com> from Bart Schaefer at "Oct 10, 1999 11:19:31 pm" To: schaefer@candle.brasslantern.com (Bart Schaefer) Date: Mon, 11 Oct 1999 09:20:49 +0100 (BST) Cc: zsh-workers@sunsite.auc.dk X-Mailer: ELM [version 2.4ME+ PL48 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Zefram Bart Schaefer wrote: > It occurs to me that printing >the prompt can actually cause commands to be executed when `promptsubst' >is set, because of $(...) substitutions. Depending on what those commands >do, that certainly could affect the behavior of a script. It's up to the user. The user sets the prompt, and if the user wants to execute commands when printing the prompt then so be it. Of course, executing commands that have side effects would be a bad idea. -zefram