Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Submitting vcs_info function
- X-seq: zsh-users 13232
- From: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
- To: zsh users <zsh-users@xxxxxxxxxx>
- Subject: Re: Submitting vcs_info function
- Date: Thu, 18 Sep 2008 02:34:20 +0200
- In-reply-to: <20080918002832.GA99337@xxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh users <zsh-users@xxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20080917201859.GU2182@xxxxxxxxxxxxxxx> <20080917233423.GA26158@xxxxxxxxxxxxxxxxxxxx> <20080917235855.GW2182@xxxxxxxxxxxxxxx> <20080918002832.GA99337@xxxxxxxxxxxxxxxxxxxx>
Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>:
> On 2008-09-18 at 01:58 +0200, Frank Terbeck wrote:
[...]
> > > Also, I don't believe that "svn info" makes any guarantees about output
> > > ordering.
> >
> > That would be unfortunate. I wouldn't mind, if there would be another
> > more machine-friendly way to extract the information... But that would
> > have to be done by a subversion-dev.
>
> *cough* Define machine-friendly? The canonical method supported by
> Subversion is to use XML.
>
> svn info --xml
>
> I'm not inclined to parse that in zsh.
Well, me neither. :)
We could however, do what we do now, and additionally introduce a
'use-perl' style, that uses perl with an appropriate module, that
parses the xml output. Unless someone writes an interface to some xml
library for zsh. :)
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
Messages sorted by:
Reverse Date,
Date,
Thread,
Author