zsh-users
 help / color / mirror / code / Atom feed
From: Geoff Wing <gcw@pobox.com>
To: User ALEX <alex@c74763-a.aurora1.co.home.com>
Cc: zsh-users@sunsite.auc.dk
Subject: Re: is this a feature of zsh-3.1.6?
Date: Mon, 27 Dec 1999 23:09:13 +1100	[thread overview]
Message-ID: <19991227230913.A12761@primenet.com.au> (raw)
In-Reply-To: <Pine.BSF.4.21.9912270108070.2876-100000@c74763-a.aurora1.co.home.com>; from alex@c74763-a.aurora1.co.home.com on Mon, Dec 27, 1999 at 01:09:51AM -0700

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 : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874


  reply	other threads:[~1999-12-27 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-27  5:48 User ALEX
1999-12-27  7:02 ` Geoff Wing
1999-12-27  8:09   ` User ALEX
1999-12-27 12:09     ` Geoff Wing [this message]
1999-12-27 13:09       ` David Kågedal
1999-12-29 10:34         ` Nemeth Ervin
1999-12-29 10:35         ` Nemeth Ervin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19991227230913.A12761@primenet.com.au \
    --to=gcw@pobox.com \
    --cc=alex@c74763-a.aurora1.co.home.com \
    --cc=zsh-users@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).