Re: [Adrian Aichner <adrian@xemacs.org>] Re: PCL-CVS shows Parser Errors in *cvs* buffer
Adrian Aichner <adrian(a)xemacs.org> writes:
Hello CVS-team!
Could you please comment why output from CVS sometimes uses 73
character =-separator lines while sometimes only 67 of them are used?
See the thread starting at
http://list-archive.xemacs.org/xemacs-beta/200201/msg00306.html
if you have the time.
Currently pcl-cvs expects 67 and reports parser errors otherwise.
A possible fix for pcvs-parse.el would be to change
(cvs-match
"===================================================================$")
to
(cvs-match
"[=]\{67,\}$")
but understanding what's going first is always a good idea :-)
I think the problem is an XEmacs problem.
I have tried to provoke the long lines in a shell buffer, but have not
succeded.
To day I ran into another instance of the what I would expect to be
the same bug.
in the *cvs* buffer I got:
/--------------------------------------
|In directory .:
|Message: Parser Error: '======cvs server: Examining etc/eicq'
| Up-To-Date 1.1 .cvsignore
|1.57 Need-Update 1.54 ChangeLog
\--------------------------------------
In the " *cvs-tmp*" buffer I have
/--------------------------------------
|===================================================================
|File: icq2tcp.c Status: Needs Patch
|
| Working revision: 1.3
| Repository revision: 1.4 /cvsroot/eicq/eicq/icq2tcp.c,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
|======cvs server: Examining etc/eicq
|===================================================================
|File: authorize-here.xpm Status: Up-to-date
|
| Working revision: 1.2
| Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
\-----------------------------------------------
Comparing to what I get in a "*shell*" buffer which is
/--------------------------------------
|===================================================================
|File: icq2tcp.c Status: Needs Patch
|
| Working revision: 1.3
| Repository revision: 1.4 /cvsroot/eicq/eicq/icq2tcp.c,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
|===================================================================
|File: infohack.el Status: Up-to-date
|
| Working revision: 1.1
| Repository revision: 1.1 /cvsroot/eicq/eicq/infohack.el,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
|cvs server: Examining etc
|cvs server: Examining etc/eicq
|===================================================================
|File: authorize-here.xpm Status: Up-to-date
|
| Working revision: 1.2
| Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
\----------------------------------------
Note that it seems that the " *cvs-tmp*" buffer does not contain the file
"infohack.el" it is entirely missing from in that buffer!
I think it has something to do with the speed in which XEmacs is able
to fetch what it gets back from the process-stream. Maybe some buffer is
just not large enough or something or something times out too fast or
what ever.
I have also tried to make a `cvs-status' with `cvs-run-process' and
`cvs-mode-run' as edebug-defun'ed. steping thorugh it manually makes
the output more stable.
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.
Jarl