zsh-workers
 help / color / mirror / code / Atom feed
From: Jean Chalard <jean.chalard@gmail.com>
To: "François-Xavier Coudert" <fxcoudert@gmail.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: [4.3 CVS] funny output with multibyte
Date: Thu, 2 Feb 2006 18:33:54 +0900	[thread overview]
Message-ID: <fb6be96e0602020133v7552893cybacb3393685147c6@mail.gmail.com> (raw)
In-Reply-To: <19c433eb0602020108k51d5a9abscece73c96079bec5@mail.gmail.com>

>   3. When the function returns, the screen turns into :
>
> pc31 ~ $ sleep 10
> azerty%
> pc31 ~ $ azerty
>
> Please note that the percent sign (%) is followed by spaces up to the
> end of the line, and that there is no newline after that.
>
> While it's not a major problem, I found that amazing. Bug or feature?

I think you are experiencing the effects of the new PROMPT_SPACES
option, which is the new solution to the NO_PROMPT_CR debate that has
been around for quite a time.
IIRC, by default zsh now print spaces that fill the terminal width and
then prints a CR. If nothing had been printed before, the last space
is on the last column but the cursor is still on the same line so the
CR makes it return at the beginning of the line so that you won't see
an empty line. If something had been printed on the line before, then
the cursor is going to be on the next line, so that your prompt won't
be printed over previous data that was not followed by a NL.

This ought to end the debate about PROMPT_CR :)

--
J
"Toi, je te trouve pas la même tête que sur la page précédente" -- Wakamiya

  reply	other threads:[~2006-02-02  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:08 François-Xavier Coudert
2006-02-02  9:33 ` Jean Chalard [this message]
2006-02-02 12:41   ` Zvi Har'El
2006-02-02 14:23     ` Vincent Lefevre
2006-02-02 15:58     ` Bart Schaefer
2006-02-02 16:27       ` Zvi Har'El

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=fb6be96e0602020133v7552893cybacb3393685147c6@mail.gmail.com \
    --to=jean.chalard@gmail.com \
    --cc=fxcoudert@gmail.com \
    --cc=zsh-workers@sunsite.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).