[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: status output and long fields

From: <cmpilato_at_collab.net>
Date: 2003-02-19 19:04:56 CET

Wolf Josef <josef.wolf@siemens.com> writes:

> cmpilato@collab.net wrote:
>
> > 'svn status' output is designed to be both human-readable and
> > machine-parsable.
>
> Truncating output that is meant to be machine readable is a bad
> thing, IMHO.
>
> > The simplest form of machine-parsable output is tabular
>
> I disagree. The simplest form of machine parsable output is
> to split by whitespace.

...except where whitespace is perfectly valid (albeit uncommon) in the
fields themselves. :-)

> Please don't output broken information.

That's fine. I think I'm gonna go with auto-sizing columns with
minimum widths and a header line. That way, a script can always read
the first line of output, hack it up to determine each column's
starting offset, and then go from there.

If anyone objects, speak now.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 19:06:31 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.