Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: cvs can't parse its arguments -- known issue? References: From: Matt Armstrong Date: Fri, 01 Nov 2002 12:17:28 -0700 In-Reply-To: ("John Morrison"'s message of "Fri, 1 Nov 2002 18:07:24 -0000") Message-ID: <87n0otaylz.fsf@squeaker.lickey.com> User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by AMaViS snapshot-20020300 "John Morrison" writes: > I've had this - a while ago I think. Try calling cvs with it's > full path... > > $ /bin/cvs ... Unfortunately, no luck. :-( Randall R Schulz writes: > I cannot replicate that failure (I get a password prompt). > > Are you invoking it from a Cygwin shell, or from CMD.exe (or > COMMAND.COM?). Win2k's CMD.EXE and Cygwin's bash give the same result. > You might want to escape the @ sign, since under certain > circumstances it's special (i.e., it's a extended shell argument > processing syntax meant to allow arguments contained in files to be > incorporated into the command line). Simply running "cvs a" gives the same error message. I suppose it is time to compile from source and debug the problem. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/