Jarl Friis <jarl(a)diku.dk> writes:
I must admit that the problem seems deeper than just cvs gives
non-parseable feedback something lurking in either the *usage* of
xemacs network features within pcl-cvs or the implementation of the
XEmacs network features.
Sorry, it seem not to be related to networking, since pcl-cvs is not
directly using the XEmacs network features, but just invokes cvs as a
process, nevertheless I consider it a XEmacs bug, but merely related
to the `start-process' function.
Jarl