From: Heinz Werner Kramski-Grote <kramski@web.de>
To: cygwin@cygwin.com
Subject: Re: Unable to use Cygwin RCS commands in Windows Emacs
Date: Thu, 21 Sep 2017 18:57:00 -0000 [thread overview]
Message-ID: <9422023.1ZBALOEEme@sandl> (raw)
In-Reply-To: <dd8f0476-ac09-bd8d-3870-0e5c2c55c2d9@SystematicSw.ab.ca>
Am Mittwoch, 20. September 2017, 22:40:53 CEST schrieb Brian Inglis:
>
> 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?
Thanks, but that doesn't work. Emacs does not see shortcuts as executables.
Regards,
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 prev parent reply other threads:[~2017-09-21 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 20:12 Heinz Werner Kramski-Grote
2017-09-20 20:40 ` Brian Inglis
2017-09-21 18:57 ` Heinz Werner Kramski-Grote [this message]
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=9422023.1ZBALOEEme@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).