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

Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes: >> >> Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes: >> >> 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* >> Jarl> I miss that buffer. hmm... I wonder why this is not created or is it Jarl> automatically deleted after the cvs command is issued maybe. Jarl> Allright, I got that one, but it is not listed under Jarl> completions when i do C-x b TAB neither is it found in Jarl> *Buffer List* C-x C-b, how sad or is that intentionally? Yes. See the documentation of list-buffers :-) Jarl> Thanks, Adrian. Jarl> For one reproduction of the bug, the only strange I can see regarding Jarl> the misbehaviour of pcl-cvs is a longer splitter line, in "*cvs*" Jarl> buffer I have That's it! This is straight out of emacs/lisp/pcvs-parse.el of GNU Emacs: (defun cvs-parse-status () (let (nofile path base-rev head-rev type) (and (cvs-match "===================================================================$") Your output contains lines with either 67 (handled today) or 73 ='s. Stefan, does this count as a bug report? Best regards, Adrian Jarl> /--------------------------------------------- Jarl> |In directory .: Jarl> |Message: Parser Error: '=========================================================================' Jarl> |Message: Parser Error: 'File: authorize-here.xpm Status: Up-to-date' Jarl> |Message: Parser Error: '' Jarl> |Message: Parser Error: ' Working revision: 1.2' Jarl> |Message: Parser Error: ' Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v' Jarl> |Message: Parser Error: ' Sticky Tag: (none)' Jarl> |Message: Parser Error: ' Sticky Date: (none)' Jarl> |Message: Parser Error: ' Sticky Options: (none)' Jarl> |Message: Parser Error: '' Jarl> \---------------------------------------------- Jarl> and in " *cvs-tmp*" I have Jarl> /--------------------------------------------- Jarl> |=================================================================== Jarl> |File: icq2tcp.c Status: Needs Patch Jarl> | Jarl> | Working revision: 1.3 Jarl> | Repository revision: 1.4 /cvsroot/eicq/eicq/icq2tcp.c,v Jarl> | Sticky Tag: (none) Jarl> | Sticky Date: (none) Jarl> | Sticky Options: (none) Jarl> | Jarl> |========================================================================= Jarl> |File: authorize-here.xpm Status: Up-to-date Jarl> | Jarl> | Working revision: 1.2 Jarl> | Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v Jarl> | Sticky Tag: (none) Jarl> | Sticky Date: (none) Jarl> | Sticky Options: (none) Jarl> | Jarl> |=================================================================== Jarl> |File: disconnect.xpm Status: Up-to-date Jarl> | Jarl> | Working revision: 1.2 Jarl> | Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/disconnect.xpm,v Jarl> | Sticky Tag: (none) Jarl> | Sticky Date: (none) Jarl> | Sticky Options: (none) Jarl> | Jarl> \---------------------------------------------- Jarl> So that longer splitter line has probably confused the parser. I Jarl> believe I have seen other reasons for parser confussions, but I will Jarl> take this up as I run in to them again. Now I know where to look (in " Jarl> *cvs-tmp*") Jarl> Even without the uniquify feature (checked `features') I have the Jarl> buffer. Thanks. Anyway I should probably have a look at these features Jarl> as use of temporary (debugging) buffers to be used in eSMS. Jarl> BTW: how do you ask XEmacs to do the kind of quoting? such as Jarl> /--------------- Jarl> |This is quoted Jarl> \--------------- Jarl> Jarl -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/