From: Frank Terbeck <ft@bewatermyfriend.org>
To: Peter <vmail@mycircuit.org>
Cc: zsh-workers@zsh.org
Subject: Re: what is the effect of a percentage sign (%) as last character on the command line
Date: Sun, 24 Jan 2010 11:58:58 +0100 [thread overview]
Message-ID: <87tyubzs3x.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <4B5C180D.8080904@mycircuit.org> (Peter's message of "Sun, 24 Jan 2010 10:51:09 +0100")
Peter writes:
> Yes, sorry , my snippet was too short:
>
> git_info() {
> ref=$(git symbolic-ref -q HEAD 2>/dev/null)
> ref=${ref#refs/heads}
> echo ${ref:+"${GREEN}[$ref]${WHITE}"}
[...]
Since you're trying to collect information from version control systems,
if you're on zsh 4.3.7 or newer, zsh includes a collection of functions
called `vcs_info' which do all the work for you. The thing is pretty
configurable, so tweaking it to your liking shouldn't be an issue.
It has support for a great number of version control systems; git is
among them (and the git backend is probably the one with the most
features).
If `vcs_info' is included in your zsh version, this should get you to
its documentation:
% MANPAGER='less -M -p GATHER' man zshcontrib
Regards, Frank
next prev parent reply other threads:[~2010-01-24 11:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B582F3C.2010709@mycircuit.org>
[not found] ` <100121080540.ZM21444@torch.brasslantern.com>
[not found] ` <4B58AB3A.7050300@mycircuit.org>
2010-01-23 10:18 ` PATCH: Add `sourcetrace' option Frank Terbeck
2010-01-23 15:46 ` Baptiste Daroussin
2010-01-23 20:16 ` Richard Hartmann
2010-01-23 21:53 ` PATCH: " Frank Terbeck
2010-01-23 22:07 ` Benjamin R. Haskell
2010-01-23 22:23 ` Frank Terbeck
2010-01-23 23:46 ` Bart Schaefer
2010-01-24 0:10 ` Frank Terbeck
2010-01-24 0:18 ` Frank Terbeck
2010-01-24 21:12 ` Peter Stephenson
2010-01-24 22:27 ` Frank Terbeck
2010-01-23 22:14 ` PATCH: " Frank Terbeck
2010-01-23 23:44 ` Bart Schaefer
2010-01-24 0:05 ` Frank Terbeck
2010-01-24 9:21 ` Peter
[not found] ` <m3fx5y2le2.fsf@klanderman.net>
[not found] ` <87hbqdu9xs.fsf@ft.bewatermyfriend.org>
[not found] ` <4B5A26BA.5080307@mycircuit.org>
[not found] ` <87fx5x6918.fsf@ft.bewatermyfriend.org>
[not found] ` <4B5ABB0D.9010504@mycircuit.org>
[not found] ` <14989d6e1001230228k22e32200s10db146bd8596dc2@mail.gmail.com>
2010-01-23 12:03 ` what is the effect of a percentage sign (%) as last character on the command line Peter
[not found] ` <2d3b879b1001211336m5b78982au96f267ea472af43d@mail.gmail.com>
[not found] ` <4B58D35D.1050208@mycircuit.org>
[not found] ` <100121182713.ZM21821@torch.brasslantern.com>
[not found] ` <4B597061.10701@mycircuit.org>
[not found] ` <100123155239.ZM27228@torch.brasslantern.com>
2010-01-24 9:51 ` Peter
2010-01-24 10:58 ` Frank Terbeck [this message]
2010-01-24 14:50 ` Peter
2010-01-26 7:52 ` Peter
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=87tyubzs3x.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=vmail@mycircuit.org \
--cc=zsh-workers@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).