From: Seth House <seth@eseth.com>
To: zsh-workers@zsh.org
Subject: Re: hg vcs_info issue
Date: Mon, 13 Feb 2012 16:54:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20120213T175121-910@post.gmane.org> (raw)
In-Reply-To: <4F392C6D.8040408@bigfoot.com>
<foudil.newie <at> bigfoot.com> writes:
> my .zshrc contains:
> autoload -Uz vcs_info
> zstyle ':vcs_info:*' enable git cvs svn hg bzr
> zstyle ':vcs_info:*' check-for-changes true
In order for the hg backend to pick up local changes you also need to
have the `get-revision` option enabled. (There is a short note about
this in the manpage.)
The reason for this is the hg backend determines if there are
uncommitted changes by running the `hg id` and looking for the '+'
character.
next prev parent reply other threads:[~2012-02-13 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 15:29 foudil.newie
2012-02-13 16:44 ` Frank Terbeck
2012-02-13 16:54 ` Seth House [this message]
2012-02-13 20:42 ` foudil.newie
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=loom.20120213T175121-910@post.gmane.org \
--to=seth@eseth.com \
--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).