From: Jordan Breeding <jordan.breeding@mac.com>
To: zsh-workers@sunsite.dk
Subject: prompt and prompt_cr option
Date: Sat, 9 Oct 2004 10:17:27 -0500 [thread overview]
Message-ID: <546D60C2-1A06-11D9-B624-000A95A6C222@mac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hello,
I have run into the problem several times of having lines of output in
the shell that don't have a newline and having the prompt overwrite
them. I did find the `setopt nopromptcr` solution but I also like
having multiline editing always work correctly. I thought that I would
try and solve both problems with the following:
setopt nopromptcr
prompt='%(1l,\n,)%! %n@%m %0~ > '
but that didn't seem to do the trick. Is there a way to force zsh to
check to see if the last character that was printed was a newline and
if it wasn't to just print one before it issues the carriage return?
Jordan
[-- Attachment #2: Type: text/enriched, Size: 673 bytes --]
<fontfamily><param>Courier</param><bigger>Hello,
I have run into the problem several times of having lines of output in
the shell that don't have a newline and having the prompt overwrite
them. I did find the `setopt nopromptcr` solution but I also like
having multiline editing always work correctly. I thought that I
would try and solve both problems with the following:
setopt nopromptcr
prompt='%(1l,\n,)%! %n@%m %0~ > '
but that didn't seem to do the trick. Is there a way to force zsh to
check to see if the last character that was printed was a newline and
if it wasn't to just print one before it issues the carriage return?
Jordan</bigger></fontfamily>
next reply other threads:[~2004-10-09 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 15:17 Jordan Breeding [this message]
2004-10-11 22:11 ` Bart Schaefer
2004-10-11 23:28 ` Danek Duvall
2004-10-12 1:52 ` Bart Schaefer
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=546D60C2-1A06-11D9-B624-000A95A6C222@mac.com \
--to=jordan.breeding@mac.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).