Re: PCL-CVS shows Parser Errors in *cvs* buffer
Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>>>>> "Jarl" == Jarl Friis
<jarl(a)diku.dk> writes:
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
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.
Ah, the buffer name is "SPC * c v s - t m p *" without the
double-quotes and spaces.
Allright, I got that one, but it is not listed under completions when i
do C-x b TAB neither is it found in *Buffer List* C-x C-b, how sad or
is that intentionally?
Thanks, Adrian.
For one reproduction of the bug, the only strange I can see regarding
the misbehaviour of pcl-cvs is a longer splitter line, in "*cvs*"
buffer I have
/---------------------------------------------
|In directory .:
|Message: Parser Error:
'========================================================================='
|Message: Parser Error: 'File: authorize-here.xpm Status: Up-to-date'
|Message: Parser Error: ''
|Message: Parser Error: ' Working revision: 1.2'
|Message: Parser Error: ' Repository
revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v'
|Message: Parser Error: ' Sticky Tag: (none)'
|Message: Parser Error: ' Sticky Date: (none)'
|Message: Parser Error: ' Sticky Options: (none)'
|Message: Parser Error: ''
\----------------------------------------------
and in " *cvs-tmp*" 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)
|
|=========================================================================
|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)
|
|===================================================================
|File: disconnect.xpm Status: Up-to-date
|
| Working revision: 1.2
| Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/disconnect.xpm,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
\----------------------------------------------
So that longer splitter line has probably confused the parser. I
believe I have seen other reasons for parser confussions, but I will
take this up as I run in to them again. Now I know where to look (in "
*cvs-tmp*")
Multiple of these stay around in my XEmacs, but I have this
;; To use this file, load it or add (require 'uniquify) to your ".emacs"
;; and set `uniquify-buffer-name-style' to one of its non-nil alternative
;; values.
(require 'uniquify)
in my .emacs.
Even without the uniquify feature (checked `features') I have the
buffer. Thanks. Anyway I should probably have a look at these features
as use of temporary (debugging) buffers to be used in eSMS.
BTW: how do you ask XEmacs to do the kind of quoting? such as
/---------------
|This is quoted
\---------------
Jarl