Re: Broken pipe error

On Tue, 24 Aug 2004 16:42:04 -0500, Ben Reser <ben@reser.org> wrote:
> On Tue, Aug 24, 2004 at 02:52:56PM -0500, 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 cat www/settings.php | gedit svn: Can't write to stream: Broken
> > pipe
>
> Sounds to me like a gedit bug. Incidentally, despite what the man page
> says I can't even get ls -l | gedit to work on my machine.
>
> However the following things work flawlessly:
>
> svn cat README | cat > foo
> svn cat README | vim -
>
> Based on these fact, I'm inclined to think gedit has some bugs in their
> support.

Certainly possible. I suspected svn because some of the subcommands worked fine, and others did not.
Note that when I pipe svn's output through another application, gedit works fine. These commands
work without a problem on my box:

$ ls -l | gedit
$ cat www/settings.php | gedit
$ svn cat www/settings.php | cat | gedit

Only when svn pipes directly to gedit does something go wonky. I discovered this when trying to
strace gedit, as suggested by Peter Lundblad. I ran

$ svn cat www/settings.php | strace gedit

and the output showed up in gedit, making the strace rather pointless :) What syntax can I use to
keep strace from intercepting gedit's stdin?

-- 
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org