From: TJ Luoma <luomat@gmail.com>
To: seanh <snhmnd@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Outputting colored zsh prompts from an external script
Date: Thu, 28 Mar 2013 17:14:20 -0400 [thread overview]
Message-ID: <CADjGqHsDjLiUVj1xDT-27BZWCxS9+NABVA-ntHAMSYKwVPzWhQ@mail.gmail.com> (raw)
In-Reply-To: <20130328202651.GA24482@kaeru>
On Thu, Mar 28, 2013 at 4:26 PM, seanh <snhmnd@gmail.com> wrote:
> Anyone know how I can make zsh call this script for PROMPT and RPROMPT,
> but fall back on a simple pure-zsh prompt if trying to call the script
> exits with non-zero? (Yes, my zsh-scripting skills really are that
> limited.)
>
> It does what I wanted from my prompt, with maybe a couple of minor
> wrinkles that could be smoothed out. If I can get custom format options
> working, it might be useful to others who want to design their own
> prompts. I'm thinking it'd work something like this, for example to get
> a zsh prompt with current working dir, virtualenv, git branch and last
> exit status, you would put something like this in your zshrc:
>
> PROMPT='$(zshprompt.py --format "{cwd:green} {venv:blue} {git:yellow} {les:red,bold}> ")'
>
> and zshprompt.py would do all the work to handle current working
> directory truncation and git branch, virtualenv and non-zero exit status
> detection, handle colours and bold etc and transform that (hopefully
> simple) string specification into the much more complex string that zsh
> needs for the prompt.
As someone who has never been able to figure out colors for zsh
prompts, I love this idea.
I don't know if there's a 'better' way to do this, but you could do it this way
FOO="$(a || b)"
if the exit code for 'a' != 0 then b will run.
next prev parent reply other threads:[~2013-03-28 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 19:23 seanh
2013-03-24 21:48 ` Christian Neukirchen
2013-03-25 13:05 ` seanh
2013-03-25 15:29 ` Bart Schaefer
2013-03-25 19:40 ` seanh
2013-03-28 20:26 ` seanh
2013-03-28 21:14 ` TJ Luoma [this message]
2013-03-29 15:07 ` 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=CADjGqHsDjLiUVj1xDT-27BZWCxS9+NABVA-ntHAMSYKwVPzWhQ@mail.gmail.com \
--to=luomat@gmail.com \
--cc=snhmnd@gmail.com \
--cc=zsh-users@zsh.org \
/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).