> The problem is that forcing a flush is a hack and doesn't solve
> anyone's actual problems. It solves a completely contrived problem
> that simply does not matter
If your main objection is that nobody really wants this anyway, I
disagree. I, as a lowly end-user, think it's very useful to pipe the
svn client output into other things. A filter to add colors or
boldface to certain status lines. A pager. grep. tee. Output should
generally be flushed per-file (for diff this means after lots of lines,
for many other commands it would be every line). Perhaps XML output
need not be buffered, since an XML document is usually not processed
until the whole thing is available to be validated.
> Where do we stop? In short, we are not going to be able to guarantee
> line-buffering to a *file* across the entire client without a much
> larger and substantial patch. We now have to audit every place we
> produce any output and add flushing.
I'd be in favor of that too - though I'd call it buffering per file
rather than per line. This makes a difference for 'diff', as well as
exempting the subcommands such as 'help' and 'info' whose output isn't
worth flushing anyway.
Auditing all the output calls certainly doesn't have to be done all at
Received on Wed Mar 8 06:11:24 2006