Re: PCL-CVS shows Parser Errors in *cvs* buffer

>>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk&gt; writes: Jarl> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com&gt; writes: >> PCL_CVS has a confusing behavior in our programming group. It always >> prints out a bunch of Parsing Errors in the *CVS* buffer. For >> example, for a cvs-update I get: >> >> ,---- >> | PCL-CVS release v2_9_9 >> | >> | Repository : :pserver:gboerrigter＠cvs.i2c-systems.com:/cvs >> | Working directory: /home/gboerrigter/workspace/dev-env/tools/ >> | >> | >> | >> | Message: Parser Error: 'CVS server: Updating .' >> | Message: Parser Error: 'CVS server: Updating togetherj' >> | Message: Parser Error: 'CVS server: Updating togetherj/bin' >> | Message: Parser Error: 'CVS server: Updating togetherj/config' >> | Message: Parser Error: 'CVS server: Updating togetherj/doc' >> | Message: Parser Error: 'CVS server: Updating togetherj/doc/images' >> | Message: Parser Error: 'CVS server: Updating togetherj/gendoc' >> | Message: Parser Error: 'CVS server: Updating xemacs' >> | Modified xemacs/emacs-i2c.el >> | Modified xemacs/init-1.el >> | Unknown xemacs/semantic.cache >> | >> | --------------------- End --------------------- >> | -- last cmd: cvs -f -z3 update -- >> `---- >> >> The Messages are very confusing, because they are not always at the >> top, but mixed up with the files. This even happens with xemacs >> -vanilla (the rest of this buffer is filled from that xemacs). >> >> Any idea, why those messages are printed? Our server runs CVS 1.10.5. Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using Jarl> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s) and Jarl> hitting cvs-status a couple of times made it go away. I have never Jarl> experienced this when using local (same computer or LAN) cvs Jarl> repository. Jarl> It could be nice if it was possible to set a cvs-debug variable to let Jarl> the cvs output go to a debug buffer to have a closer look at what Jarl> pcl_cvs receives. How about C-x b runs the command switch-to-buffer *cvs-tmp* Gerd, can you see anything wrong in that buffer?