On Tue, 24 Aug 2004, Ben Gollmer wrote:
> Ran into an issue recently when trying to pipe svn's output into gedit (GEdit 2.6.0, Fedora Core
> 2):
>
> svn, version 1.0.6 (r10360)
> compiled Jul 20 2004, 07:03:06
>
> $ svn blame www/settings.php | gedit
> svn: Can't write to stream: Broken pipe
>
> $ svn cat www/settings.php | gedit
> svn: Can't write to stream: Broken pipe
>
> $ svn info www/settings.php | gedit
> (output appears in gedit as expected)
>
> Other commands, such as ls -l | gedit, also work fine. I searched the issue tracker to see if this
> was a known bug, but nothing turned up. To my untrained eye, it looks like the problem lies in the
> usage of svn_stream_printf() vs svn_cmdline_printf().
>
Could you strace the processes and check that gedit actually reads
everything that svn writes before closing the pipe?
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 24 22:45:53 2004