Re: [request] please test new pcl-cvs
Sorry, I have no way to test NT at this point. Wow, I didn't know
pcl-cvs used to work on it. That's encouraging at least...
First, which pcl-cvs package version is broken? 1.30?
Can you try to determine whether the problem is pcl-cvs or XEmacs by
trying the newer pcl-cvs on the older XEmacs and vice-versa?
Which version of CVS appears first on your path (run "cvs -v")? One
change I made was to just use the one found on your path, and I nuked
the kludgy code that was trying to locate CVS. If "which cvs" is not
the right one to use, try setting `cvs-program' to a string containing
the full path.
The message below indicates CVS is being invoked incorrectly, so I
guess it is most likely an XEmacs or choice of shell problem.
greg
>>>> "Malcolm" == Malcolm Box
<malcolm(a)brownale.demon.co.uk> writes:
Malcolm>
> Those of you who use pcl-cvs, could you please beat on it as much
as
> possible and give me feedback. In particular, if there are things the
> parser does not handle, I'd like to add code to handle those things.
> Fortunately the new parser will just insert a warning in the *cvs*
> buffer and continue, unlike the old one.
Malcolm>
Malcolm> Unfortunately for me pcl-cvs is completely broken on Win NT. I have had
Malcolm> pcl-cvs working on b38, but the latest beta hoses it. This is despite
Malcolm> much better sub-process support - W3, efs and shell all work much
Malcolm> better.
Malcolm>
Malcolm> With cvs-shell set to the default "/bin/sh" (which is probably
broken
Malcolm> for NT anyway) and cygwin bash at /bin/sh I get the following:
Malcolm>
Malcolm> Message:
Malcolm> Parser Error: 'Usage: cvs [cvs-options] command
Malcolm> [command-options-and-arguments]'
Malcolm>
Malcolm> Message:
Malcolm> Parser Error: ' where cvs-options are -q, -n, etc.'
Malcolm>
Malcolm> etc for all the rest of what cvs puts out when it doesn't recognise the
Malcolm> command. The trick appears to be to quote the arguments to
Malcolm> start-process after the "-c" so the command line looks like
Malcolm> /bin/sh -c "cvs update" rather than /bin/sh -c cvs update.
Malcolm>
Malcolm> With cvs-shell set to cmd.exe (arguably the correct choice on NT - it
Malcolm> should probably be initialised from shell-file-name) I get no output
Malcolm> whatsoever - no output is produced from the sub-process.
Malcolm>
Malcolm> This was working with pcl-cvs-1.12 and b38 (or earlier) with shell set
Malcolm> to cmd.
Malcolm>
Malcolm> Hope this helps - if I find a solution I'll send in some patches.
Malcolm>
Malcolm> Malcolm
Malcolm>