From: Adam Spiers <adam@spiers.net>
To: zsh users <zsh-users@sunsite.auc.dk>
Subject: Re: color prompt
Date: Tue, 7 Dec 1999 01:13:06 +0000 [thread overview]
Message-ID: <19991207011306.A4276@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <19991205221528.A25782@uiuc.edu>
Matt Garman (garman@uiuc.edu) wrote:
> On Mon, Dec 06, 1999 at 12:51:48AM +0000, Adam Spiers wrote:
> > Matt Garman (garman@uiuc.edu) wrote:
> > > Is there any way I can colorize my zsh prompt?
> > The latest development versions of zsh 3.1.6 have a themeable prompt
> > system with plenty of (ahem) nice colours. Even if you don't want to
> > use a bleeding edge version, the relevant shell-scripts should serve
> > as examples of how to get colours in your prompt.
> > For information on where to get the latest development versions, and
> > very brief instructions on how to use the prompt theme system, see:
>
> I have zsh 3.1.6 installed, but I don't have the promptinit function in
> my distrib. Does that mean, then, that there are different versions of
> 3.1.6? How do I know which 3.1.6 is the newest in that case?
An `echo $ZSH_VERSION' will always give you a clue as to
(approximately) which version you are using.
There are many versions of 3.1.6 floating around:
3.1.6 -- The last official development version. There have
been many MANY improvements since this; if you don't
mind using unstable versions, you might as well reap
the many benefits of using one of the versions below
instead of this one:
3.1.6-pws-x -- Official intermediate development versions compiled
by Peter Stephenson (pws) from selected patches from
zsh-workers. Sometimes released once a week,
sometimes less often.
3.1.6-bart-y -- "Intermediate intermediate" releases from Bart
Schaefer, to make developer's lives easier while pws
was away.
3.1.6-cvs -- Public CVS repository maintained by Tanaka Akira. The
intermediate releases above are always merged into
the main branch, so this source tree represents the
current development tree the closest on average.
If you were to put them on a scale, it would be something like this:
3.x.y, x even 3.x.y, x odd intermediate devel tanaka-cvs
(e.g. 3.0.7) (e.g. 3.1.6) releases (pws, bart)
<---------------------------------------------------------------------->
least often released / most often released /
most stable most bleeding edge
See the URL I mentioned before for where to get these in various formats:
http://www.new.ox.ac.uk/~adam/computing/zsh/
> In the mean time, I tried putting something like this in my ~/.zshrc file:
>
> fg_black="$(echo -n '\e[1;30m')"
As you'll notice if you look at Functions/Misc/colors from once of the
recent development versions (not 3.1.6 pure), this could be written
as:
fg_black=$'\e[1;30m'
Your cursor positioning question has already been answered elsewhere.
Adam
prev parent reply other threads:[~1999-12-07 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19991205180334.A25275@uiuc.edu>
1999-12-06 0:51 ` Adam Spiers
1999-12-06 4:15 ` Matt Garman
1999-12-06 5:24 ` Dan Nelson
1999-12-07 1:13 ` Adam Spiers [this message]
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=19991207011306.A4276@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--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).