From: Wayne Davison <wayned@users.sourceforge.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: PROMPT_SP
Date: Sat, 23 Jul 2005 09:53:01 -0700 [thread overview]
Message-ID: <20050723165301.GB16571@blorf.net> (raw)
In-Reply-To: <1050723135554.ZM19813@candle.brasslantern.com>
On Sat, Jul 23, 2005 at 01:55:54PM +0000, Bart Schaefer wrote:
> The echotc command now requires the termcap module ... I can't decide
> whether I'm more concerned that (1) the module won't be available, or
> that (2) the RI capability won't be. However, neither concern is very
> serious.
And I do still give the simpler 1-echo alternative for those that can't
use the 3-echo version. There's probably even be a way to code up a
check for the termcap module and the RI capability, but that seems like
overkill to me.
> ... I've begun to wonder whether we're only replacing one complaint ("the
> prompt overwrites my output") with another ("'echo -n' doesn't work, I
> always get a newline").
Interesting! One way to deal with that would be to output some
characters other than spaces that would only become visible when zsh
makes a partial line visible. For instance:
echotc so
echo -n '[EOL]'
echotc se
echotc RI $((COLUMNS - 7))
echo -n ' '
That puts a standout-string "[EOL]" at the end of the output. I like
the extra indication that the output did not end with a newline. What
do you think?
..wayne..
next prev parent reply other threads:[~2005-07-23 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 18:25 Wayne Davison
2005-07-15 17:55 ` Wayne Davison
2005-07-16 16:06 ` Bart Schaefer
2005-07-16 19:56 ` Wayne Davison
2005-07-18 10:32 ` Peter Stephenson
2005-07-18 18:13 ` Wayne Davison
2005-07-23 13:55 ` Bart Schaefer
2005-07-23 16:53 ` Wayne Davison [this message]
2005-07-23 17:19 ` Wayne Davison
2005-07-24 5:27 ` Bart Schaefer
2005-07-24 6:10 ` Wayne Davison
2005-07-24 9:49 ` Bart Schaefer
2005-07-26 21:53 ` Wayne Davison
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=20050723165301.GB16571@blorf.net \
--to=wayned@users.sourceforge.net \
--cc=schaefer@brasslantern.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).