From: Heinz Werner Kramski-Grote <kramski@web.de>
To: cygwin@cygwin.com
Subject: Unable to use Cygwin RCS commands in Windows Emacs
Date: Wed, 20 Sep 2017 20:12:00 -0000 [thread overview]
Message-ID: <2609139.qye4Nty6R7@sandl> (raw)
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.
Heinz
--
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
next reply other threads:[~2017-09-20 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 20:12 Heinz Werner Kramski-Grote [this message]
2017-09-20 20:40 ` Brian Inglis
2017-09-21 18:57 ` Heinz Werner Kramski-Grote
2017-09-20 21:01 ` cyg Simple
2017-09-21 19:09 ` Heinz Werner Kramski-Grote
2017-09-22 2:26 ` David Standish
2017-09-22 10:31 ` Heinz Werner Kramski-Grote
2017-09-22 16:51 ` Andy Moreton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2609139.qye4Nty6R7@sandl \
--to=kramski@web.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).