From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27435 invoked from network); 21 Sep 2005 03:42:19 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 21 Sep 2005 03:42:19 -0000 Received: (qmail 45769 invoked from network); 21 Sep 2005 03:42:13 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 21 Sep 2005 03:42:13 -0000 Received: (qmail 11580 invoked by alias); 21 Sep 2005 03:42:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 21742 Received: (qmail 11571 invoked from network); 21 Sep 2005 03:42:08 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 21 Sep 2005 03:42:08 -0000 Received: (qmail 45479 invoked from network); 21 Sep 2005 03:42:08 -0000 Received: from dsl3-63-249-88-2.cruzio.com (HELO dot.blorf.net) (63.249.88.2) by a.mx.sunsite.dk with SMTP; 21 Sep 2005 03:42:07 -0000 Received: by dot.blorf.net (Postfix, from userid 1000) id DDF408DA1; Tue, 20 Sep 2005 20:42:06 -0700 (PDT) Date: Tue, 20 Sep 2005 20:42:06 -0700 From: Wayne Davison To: Bart Schaefer Cc: zsh-workers@sunsite.dk Subject: Re: Prompt oddity when running as "sh" (4.3.0-dev) Message-ID: <20050921034206.GA2955@blorf.net> References: <1050920160050.ZM9532@candle.brasslantern.com> <20050920163045.GE28681@blorf.net> <1050921021110.ZM9892@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1050921021110.ZM9892@candle.brasslantern.com> User-Agent: Mutt/1.5.9i X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 On Wed, Sep 21, 2005 at 02:11:10AM +0000, Bart Schaefer wrote: > Shouldn't that be "%B%S%#%s%b" ? (That was my original suggestion, in > any event.) ^^ I'm not sure why we'd want the character to change between % and # depending on the user being root. What was your reasoning? ..wayne..