[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lost process output in pipe between Emacs and CVS
From: |
Richard Stallman |
Subject: |
Re: Lost process output in pipe between Emacs and CVS |
Date: |
Tue, 9 Jul 2002 12:51:48 -0600 (MDT) |
CVS uses stdio, and stdio doesn't work very well with non-blocking
file descriptors. CVS can detect the error easily enough, but at that
point stdio has already thrown away the buffer full of data, and CVS
hasn't recorded it anywhere. While in principle CVS could switch to
not use stdio, that would be a fairly substantial change.
Many programs use stdio, and these programs ought to work when run
under ssh. This suggests that ssh and stdio are responsible for the
problem, and one or the other of them should be fixed.
It would be best to fix stdio, I think. What platform is CVS running
on when it fails? Does stdio in GNU libc handle non-blocking file
descriptors properly? If not, we can fix it.
- Lost process output in pipe between Emacs and CVS, Stefan Monnier, 2002/07/08
- Re: Lost process output in pipe between Emacs and CVS, Ian Lance Taylor, 2002/07/08
- Re: Lost process output in pipe between Emacs and CVS, Ian Lance Taylor, 2002/07/08
- Re: Lost process output in pipe between Emacs and CVS, Richard Stallman, 2002/07/08
- Re: Lost process output in pipe between Emacs and CVS, Richard Stallman, 2002/07/11
- Re: Lost process output in pipe between Emacs and CVS, Derek Robert Price, 2002/07/19
- Re: Lost process output in pipe between Emacs and CVS, Larry Jones, 2002/07/19
- Re: Lost process output in pipe between Emacs and CVS, Stefan Monnier, 2002/07/19
- Re: Lost process output in pipe between Emacs and CVS, Ian Lance Taylor, 2002/07/19
- Re: Lost process output in pipe between Emacs and CVS, Richard Stallman, 2002/07/21
- Re: Lost process output in pipe between Emacs and CVS, kevin wang, 2002/07/24