On Tue, 24 Aug 2004 17:40:05 -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, 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
> You know I have a theory on what's going on here...
>
> The commands you say are not working are commands that muts go to the
> network to talk to the server to get information.
>
> Try these two commands:
>
> svn stat | gedit
>
> svn stat -u | gedit
>
> If the first one works and the second one fails then what's happening
> is gedit isn't seeing input fast enough so it stops watching stdin
> (probably closes it, thus the Broken pipe message) and assumes you're
> just starting it with no document selected.
>
> So my bet is this is a side effect of gedit trying to infer what you
> want, rather than you just being able to say what you want by say doing:
> foo | gedit -
Well, you are correct. svn stat works, and svn stat -u doesn't. Only with stat, I don't get the
'Can't write to stream: Broken pipe' error. That's probably not relevant though.
--
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 26 20:22:45 2004