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.
Unfortunately for me pcl-cvs is completely broken on Win NT. I have had
pcl-cvs working on b38, but the latest beta hoses it. This is despite
much better sub-process support - W3, efs and shell all work much
better.
With cvs-shell set to the default "/bin/sh" (which is probably broken
for NT anyway) and cygwin bash at /bin/sh I get the following:
Message:
Parser Error: 'Usage: cvs [cvs-options] command
[command-options-and-arguments]'
Message:
Parser Error: ' where cvs-options are -q, -n, etc.'
etc for all the rest of what cvs puts out when it doesn't recognise the
command. The trick appears to be to quote the arguments to
start-process after the "-c" so the command line looks like
/bin/sh -c "cvs update" rather than /bin/sh -c cvs update.
With cvs-shell set to cmd.exe (arguably the correct choice on NT - it
should probably be initialised from shell-file-name) I get no output
whatsoever - no output is produced from the sub-process.
This was working with pcl-cvs-1.12 and b38 (or earlier) with shell set
to cmd.
Hope this helps - if I find a solution I'll send in some patches.
Malcolm