From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4884 invoked by alias); 17 Sep 2012 16:57:38 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17279 Received: (qmail 15300 invoked from network); 17 Sep 2012 16:57:36 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, HTML_MESSAGE,RCVD_IN_DNSWL_LOW,T_DKIM_INVALID autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 74.125.82.171 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Cio8EGdm/1y7f0G3DcLh/sXxKodrAcuF0n6FQOBnhv4=; b=j1jcHgRaC6ZngSBGAzVe8fpPp1qoiyU07N6zfzJmnZgqZ3lKoPkRACn/snWLeytt3l LHvIvbWrDArFiK/4uqYtlWrgIUiIIE4u9UHCBod3sonV9wYorbofUwL8Gf3KMqRFRaUB a7y/whpffmnzfos5gaWS1g6jHMheG2IZLVb/BchpmdNdYaZpPkJfu33XpnadunPhVLmI ccRyq94xQljc5lJlqzFrXborO9W+6G/2cuaXZY957dUHLuyQ2qf9ScAqJ3XJVWevYTVO RapIB5EkJjFZu7wAlMk3yxTA8zD2ej7EFRSeYVCD6bpbZN1hWH9ZWGNtnNY53QcCJMta VR8w== MIME-Version: 1.0 Sender: whiteinge@gmail.com In-Reply-To: <87vcfca9sa.fsf@ft.bewatermyfriend.org> References: <87boh4bt5l.fsf@ft.bewatermyfriend.org> <877grsbrz7.fsf@ft.bewatermyfriend.org> <87zk4oabam.fsf@ft.bewatermyfriend.org> <87vcfca9sa.fsf@ft.bewatermyfriend.org> Date: Mon, 17 Sep 2012 09:57:29 -0700 X-Google-Sender-Auth: E6OgXdBWDFGcbLGPbzN68n9ijS0 Message-ID: Subject: Re: vcs_info on a hg repository with a git subrepository; actionformats works ok, formats does not From: Seth House To: Frank Terbeck Cc: Ioannis Koutras , zsh-users@zsh.org Content-Type: multipart/alternative; boundary=f46d04138a5748fef604c9e8ab08 --f46d04138a5748fef604c9e8ab08 Content-Type: text/plain; charset=UTF-8 That may be the answer. That said, their addition of git commands to the debug output isn't outputting terribly useful info. I wonder if that is intentional. Especially since the output differs with the presence of the -r flag. (I will research.) The --debug flag is used to get hg to output the full sha. Perhaps there is a better way to get all req'd info. On Sep 17, 2012 9:34 AM, "Frank Terbeck" wrote: > Seth House wrote: > [...] > > The output for the newer Mercurial is below: > > > > % hg --debug id -i -n -b > > nested: git --version > > nested: git config --bool core.bare > > nested: git rev-parse HEAD > > nested: git update-index -q --refresh > > nested: git diff-index --quiet HEAD > > 4a0f6db684a9b73ca8da117d2e368d309385bc20 1 default > > ...so, what's the solution? read data until there is no more to read and > then use the data from the last line of the output? > > Regards, Frank > --f46d04138a5748fef604c9e8ab08--