From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Cc: michael.soegtrop@intel.com
Subject: Re: Interest in Emacs patched to handle Windows paths?
Date: Fri, 26 Jul 2019 20:03:00 -0000 [thread overview]
Message-ID: <28ad7018743208ae438978d13760b765@mail.kylheku.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FDB3DF2@IRSMSX102.ger.corp.intel.com>
On 2019-07-26 10:11, Soegtrop, Michael wrote:
> Dear Cygwin Team and Users,
>
> In May I modified Emacs for Cygwin so that it can truly handle Windows
> paths.
You might be interested in the Cygnal project:
http://www.kylheku.com/cygnal/
In this project, I modified Cygwin itself to use Windows paths.
There are some other changes, of course, all documented in detail.
I use Cygnal for a native Windows port of the TXR language. This is just
the
Cygwin version of txr.exe bundled with the patched cygwin.dll (plus some
additional needed libs), wrapped up in an installer.
There is no separate build; just packaging.
Cygnal isn't an environment; it doesn't replace Cygwin. It's a way of
deploying Cygwin programs stand-alone to Windows users who expect
certain
Windows conventions, while retaining the advantages of Cygwin's large
and detailed POSIX API footprint.
--
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:[~2019-07-26 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 17:12 Soegtrop, Michael
2019-07-26 18:15 ` Ken Brown
2019-07-26 20:03 ` Kaz Kylheku [this message]
2019-07-26 20:08 ` Soegtrop, Michael
2019-07-27 18:27 Kaz Kylheku
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=28ad7018743208ae438978d13760b765@mail.kylheku.com \
--to=920-082-4242@kylheku.com \
--cc=cygwin@cygwin.com \
--cc=michael.soegtrop@intel.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).