From: davidk@lysator.liu.se (David Kågedal)
To: zsh-users@sunsite.auc.dk
Subject: Re: is this a feature of zsh-3.1.6?
Date: 27 Dec 1999 14:09:00 +0100 [thread overview]
Message-ID: <jpn1qwcyz7.fsf@venom.lysator.liu.se> (raw)
In-Reply-To: Geoff Wing's message of "Mon, 27 Dec 1999 23:09:13 +1100"
Geoff Wing <gcw@pobox.com> writes:
> 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.
I use no_prompt_cr, and I have a right prompt and stuff. Of course
the command line gets a little messes up when programs don't finish
their output with a newline, but that can easily be cleared up with
ctrl-L. I prefer to clear the mess up myselft rather than having zsh
hide output.
--
David Kågedal
next prev parent reply other threads:[~1999-12-27 13: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
1999-12-27 13:09 ` David Kågedal [this message]
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=jpn1qwcyz7.fsf@venom.lysator.liu.se \
--to=davidk@lysator.liu.se \
--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).