X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Th4QTuf1cnxhmDOd
	cGutyxJ4vCVi+S9r1iFZuHWzFAbGPlkC2Ernw0XdIHW4V1rAMEoHllgGr6Tw5uB/
	GgX74I1XfxDPuxeEGkYRWZi1F1hdiCRcKLFErGqCDAITV7VUxKcQdgOKXyPO6Q9q
	bXleU8OeFgq8tjRgzzUEJkZLWNk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=dZWfQAS8YmgY62N2iVPLgO
	Wtgls=; b=DMGVPdknZt8VDOGYNy0IaYmOyXcfJXs2z5QZa7yTKJECX5zmQ829b+
	Sw2S8nbAmqAXcYblgEpqN3ks2sNXeKRj1GONP4G4ryNrRdWQpaF4PPuixJQk66Dk
	xEcYT9BWugZIDysL/0AFhWZZCJcLC5bUJF6BB2vDOkz8ziIfthe0E=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.3 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*R:D*ca, Kramski-Grote, kramski-grote, KramskiGrote
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=e552ceh/ c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=izVC_YfdFgwZI91fw0gA:9 a=QEXdDO2ut3YA:10
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: Unable to use Cygwin RCS commands in Windows Emacs
To:	cygwin AT cygwin DOT com
References:	<2609139 DOT qye4Nty6R7 AT sandl>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<dd8f0476-ac09-bd8d-3870-0e5c2c55c2d9@SystematicSw.ab.ca>
Date:	Wed, 20 Sep 2017 14:40:53 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version:	1.0
In-Reply-To:	<2609139.qye4Nty6R7@sandl>
X-CMAE-Envelope:	MS4wfAS481AJWWXH2YdwYae5yspKoWC1DiBHZCoWMVkGfxtK40DaEUxULCbz6QKiy9v65OuOxvphQOWSjIhatEYSdwOm7Lbv0War/XK2BP2CAu6vjQXSt0+X Fz+/jW7qNJi4ZsJjFg0ENtACfwxPGYDTHWoZkqRihxMzwvsbrjnDJC8Fvp0g/Bx3yR69/klRS+tq/w==
X-IsSubscribed:	yes

On 2017-09-20 14:12, Heinz Werner Kramski-Grote wrote:
> At some point in history, /usr/bin/co, /usr/bin/ci, /usr/bin/rlog etc. turned 
> from .exe into shell scripts, which are now wrappers for the main program 
> /usr/bin/rcs.exe. 
> 
> However, these shell scripts can not be called directly from a Windows command 
> line and moreover can not be invoked by a Windows (not Cygwin) Emacs (25.2 
> currentlly).
> 
> Windows Emacs expects external Windows commands/binaries like co, ci, rlog, 
> etc.  to exist somewhere in the PATH. The commands to be invoked for version 
> control with RCS are hardcoded into "C:\Program Files\emacs-25.2\share\emacs
> \25.2\lisp\vc\vc-rcs.el" and can not be customized, as far as I know.
> 
> I tried to create wrapper scripts for Windows too (co.cmd, ci.cmd etc. -  
> basically just "c:\cygwin\bin\bash -c '/bin/%~n0 %*'"), which work to some 
> extend on the Windows command line, but mostly fail when invoked from Emacs' 
> version control functions.
> 
> The most recent native Windows port of RCS I could find is version 5.7 and 
> dates back to 1999. In addition, it uses filenames like "RCS/somefile" instead 
> of the usual "RCS/somefile,v", so this does not look like a way to go either. 
> 
> I'm clueless now. Does someone successfully use Cygwin's RCS commands in 
> Windows Emacs? Is there still an older Cygwin RCS package around which 
> contains "real" co.exe, ci.exe etc.? 
> 
> Any help is greatly appreciated.

Tried creating shortcuts to the commands in $HOME/bin/, running C:\Cygwin\bin\sh
/bin/cmd %*, and adding $HOME/bin to the start of your Windows PATH?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -