[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-02-19 21:12:07 CET

cmpilato@collab.net writes:

> 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.

Sounds good to me.

At the moment, *far* more human eyeballs parse 'svn st -v' than
computer programs. This sort of output is intolerable to me:

               14 1 jrandom A/D/G/pi
               14 1 jrandom A/D/G/rho
               14 1 jrandom A/D/G/tau
               14 6 anonymous A/D/H
               14 1 jrandom A/D/H/chi
               14 6 anonymous A/D/H/omega
               14 1 jrandom A/D/H/psi

... if my eyeball can't see a single left-alignment in the final
column, I go insane. It makes reading the list of paths almost
impossible.

I'm glad you're fixing it, CMike. :-)

---------------------------------------------------------------------
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:14:06 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.