> > That will mean a additional line in the output, and the way I use
> > Subversion it will mean that I get a "please wait" message immediately
> > before the command exits. Is this new output really necessary? It's
> > not really an improvement in every case.
>
> True. It would be a (very) mild annoyance to those who are not having
> a problem.
>
> But to those who *are* having a problem, it's a big difference -- to
> them, it looks like Subversion is stuck, and this would clue them in
> that it's not. After a few minutes (a realistic amount of time if you
> have a big enough tree combined with a slow enough disk) of mysterious
> inaction, anyone would be tempted to hit ^C.
>
> I'm certainly not wedded to the idea of an extra line of output, if we
> can think of a better solution to this problem.
How about testing if STDOUT (or STDERR) is a terminal, and just print a
rotating line ( one of -\|/, followed by \r ) there if it is?
So no output in logfiles, just a sign that things are being done.
Of course, there's nothing like this in svn now - so that would be a
precedent.
If there will be some kind of status-indicator for terminals we could as well
count the locks we made and later show a percentage (and a graph! Oh, I like
graphs :-) to show how we're doing ...
Regards,
PMarek
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 11 07:39:42 2003