From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12825 invoked from network); 27 Dec 1999 12:09:33 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Dec 1999 12:09:33 -0000 Received: (qmail 14918 invoked by alias); 27 Dec 1999 12:09:19 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2813 Received: (qmail 14911 invoked from network); 27 Dec 1999 12:09:17 -0000 Date: Mon, 27 Dec 1999 23:09:13 +1100 From: Geoff Wing To: User ALEX Cc: zsh-users@sunsite.auc.dk Subject: Re: is this a feature of zsh-3.1.6? Message-ID: <19991227230913.A12761@primenet.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from alex@c74763-a.aurora1.co.home.com on Mon, Dec 27, 1999 at 01:09:51AM -0700 Organization: PrimeNet Computer Consultancy User ALEX wrote about Re: is this a feature of zsh-3.1.6?: :On 27 Dec 1999, Geoff Wing wrote: :: % setopt nopromptcr # (or unsetopt promptcr) :Thanks for the answer. Do you know why this option is enabled by default?! A couple of reasons are: 1) It's always been enabled by default (in the first widespread release version 2.0 it was called no_prompt_clobber and changed to no_prompt_cr in 2.2) so it's still enabled for backward compatibility. 2) It means that when line editing in command mode, the shell can reliably move the cursor (and text) around the line. Without knowing where the cursor is in absolute (horizontal) terms the shell can't know if it has crossed a line boundary; how the cursor behaves on crossing line boundaries has widely different behaviours depending upon the terminal. In short, if you use this then you're pretty much stuck with using short single line command lines (and no right prompt) when any text is spewed up prior to the prompt. Regards, -- Geoff Wing : Work URL: http://www.primenet.com.au/ Rxvt Stuff : Ego URL : http://pobox.com/~gcw/ Zsh Stuff : Phone : (Australia) 0413 431 874