"Brian W. Fitzpatrick" <fitz@collab.net> writes:
> > >> This has long bothered me too. In 'svn status' output, we print 12
> > >> columns worth of username. But in 'svn ls', we only print 8 columns
> > >> of username.
> > [...]
> > >> It would be an incompatible API change to go to 12 as the default for
> > >> 'ls -v' now. But it would be okay to add a run-time configuration
> > >> parameter to control this width. How would people feel about that?
> > >
> > > I think that it's silly to add a configuration option to fix what is, in
> > > my opinion, a bug. I don't see how this is the lesser of two evils
> > > (breaking compatibility being the other "evil").
> > >
> > > If we didn't have an API that folks can use from C, Java, Python, and
> > > Perl, and parsing output from svn was your only recourse, I might bend
> > > on this. As it stands, I'm strongly -1 on adding a run-time config
> > > parameter. This is a bug, let's just fix it.
> >
> > What is the bug that you see? What do you see as a suitable "fix"?
>
> That it's not the same width as it is in 'svn status' output.
The situation is more subtle than that, as a lurker just pointed out
to me privately:
> Please note that, including spaces, 'svn ls -v' prints "exactly eight"
> characters, chopping if necessary, while 'svn st -v' prints "at least
> twelve" characters and it does not chop anything.
Does this affect the proposed fix?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 14 19:38:44 2005