Stefan Haller wrote:
> Mattias Engdegård <mattias@virtutech.se> wrote:
>
>
>> haller@ableton.com (Stefan Haller) writes:
>>
>>
>>> To recap: For operations that can take a long time to complete, such as
>>> status or update, it is nice to flush stdout after every line of status
>>> output, to give nicer behaviour when piping output into, say, a pager,
>>> or tee.
>>>
>> What about the following trivial script:
>>
>> [ pty wrapper script snipped ]
>>
>
> This is not an acceptable solution; users shouldn't have to do this. If
> you type "make | tee log.txt", you expect to see the ouput while it
> happens, right? If this works well for make, I don't see why some
> people insist it shouldn't also for svn.
>
> Besides, it is probably not very portable. I'm not sure if it works in
> cygwin, for example (I haven't tried).
>
>
>> (If you insist in changing the client, why not add a global option
>> which just sets the stdout buffering to line mode?)
>>
>
> There shouldn't be an option for something like this. It should "just
> work", without the user having to do anything.
>
> And you don't really want line mode anyway. You want flushing after
> chunks of information; in many cases this is after every line, but for
> log it is after each entry, and for diff it is after each file.
>
> I really think that judicious flushing in selected places is the right
> thing to do to solve this.
>
I agree, and +1 to committing your patch and ending this discussion. If
nobody beats me to it, I'll look into committing this over the week-end.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 20 09:23:17 2006