From: Bart Schaefer <schaefer@brasslantern.com>
To: Ian Lynagh <igloo@earth.li>
Cc: zsh-users@sunsite.dk
Subject: Re: Length of %? in prompt
Date: Thu, 28 Feb 2002 13:00:06 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0202281150320.710-100000@ns1.sodaware.com> (raw)
In-Reply-To: <20020228171254.GA32284@stu163.keble.ox.ac.uk>
On Thu, 28 Feb 2002, Ian Lynagh wrote:
> What I'm doing is something like this:
>
> /--stuff--more stuff--some more stuff--------------------
>
> and I am then truncating this to the screen width with \ (using / and \
> for top-left and top-right corner characters respectively). The border
> is in graphics mode and bold cyan while the various stuffs are in
> various colours and normal text mode, so if it gets truncated in the
> middle of them I am getting a text letter k in whatever colour happens
> to be there. Therefore I want to set the colour and have a ^N in the
> truncating string.
OK, the point is that you don't want the upper right corner to be a
different color or character just because the string was truncated. Thus
what you want to do here is sacrifice one additional character so that the
"truncating string" (let's call it the "ellipsis" since it plays the role
of the "..." in a truncated sentence) and the truncated string (let's call
that the "sentence" for the same reason) both end with the same character,
and that character is not a terminal control sequence. Then, _after_ the
%<< that closes the sentence, you emit the correct color and the upper
right corner. Don't worry about changing the color only if it's wrong,
just always force it to be right.
So something like (still using / and \ rather than graphics chars):
UL="$fg_bold[cyan]/" # upper left
UR="$fg_bold[cyan]\\" # upper right
PS1='$UL%$((COLUMNS-4))>->-stuff--more stuff--some more stuff---%<<$UR
\$ $reset_color'
(There's an embedded newline in that PS1 example.)
For a much more complicated example of this same thing, see
Functions/Prompts/prompt_adam2_setup
in the 4.0.4 distribution.
next prev parent reply other threads:[~2002-02-28 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 16:05 Ian Lynagh
2002-02-26 16:48 ` Peter Stephenson
2002-02-26 17:10 ` Bart Schaefer
2002-02-26 18:08 ` Ian Lynagh
2002-02-26 18:26 ` Bart Schaefer
2002-02-26 18:42 ` Ian Lynagh
2002-02-26 19:21 ` Bart Schaefer
2002-02-28 15:34 ` Ian Lynagh
2002-02-28 16:45 ` Bart Schaefer
2002-02-28 17:12 ` Ian Lynagh
2002-02-28 21:00 ` Bart Schaefer [this message]
2002-03-01 12:38 ` Ian Lynagh
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=Pine.LNX.4.44.0202281150320.710-100000@ns1.sodaware.com \
--to=schaefer@brasslantern.com \
--cc=igloo@earth.li \
--cc=zsh-users@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).