bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Adrian Aichner <address@hidden>] Re: PCL-CVS shows Parser Errors in *cv


From: Adrian Aichner
Subject: [Adrian Aichner <address@hidden>] Re: PCL-CVS shows Parser Errors in *cvs* buffer
Date: 24 Jan 2002 13:06:03 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp (Windows))

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 :-)

Thanks in advance,

Adrian

--- Begin Message --- Subject: Re: PCL-CVS shows Parser Errors in *cvs* buffer Date: 23 Jan 2002 12:11:44 +0100 User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp (Windows))
>>>>> "Jarl" == Jarl Friis <jarl@diku.dk> writes:

    Jarl> Adrian.Aichner@t-online.de (Adrian Aichner) writes:
    >> >>>>> "Jarl" == Jarl Friis <jarl@diku.dk> writes:
    >> 
    Jarl> Adrian.Aichner@t-online.de (Adrian Aichner) writes:
    >> >> >>>>> "Jarl" == Jarl Friis <jarl@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.

    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*")

    >> 
    >> 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.

    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/


--- End Message ---

-- 
Adrian Aichner
 mailto:adrian@xemacs.org
 http://www.xemacs.org/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]