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: Sat, 27 Jul 2019 18:27:00 -0000 [thread overview]
Message-ID: <23a9789b9880e266b34f92c2728cdfa4@mail.kylheku.com> (raw)
On 2019-07-26 13:08, Soegtrop, Michael wrote:
> Dear Kaz,
>
>> You might be interested in the Cygnal project:
>> http://www.kylheku.com/cygnal/
>
> from your description I would think this doesn't work for Emacs. Emacs
> has its own functions for path management, e.g. to decide what an
> absolute path is.
Yes, like this: :)
C:\Users\kaz>txr
This is the TXR Lisp interactive listener of TXR 221.
Quit with :quit or Ctrl-D on empty line. Ctrl-X ? for cheatsheet.
1> (abs-path-p "C:\\foo")
t
2> (abs-path-p "C:foo")
nil
3> (abs-path-p "/foo")
t
Cygnal is not a magic fix for programs that manipulate path; it provides
a POSIX-like system interface, but which takes Windows paths. If the
program manipulates paths, that has to be ported/extended to support
Windows paths.
What it provides is that the open() system call and others understand
drive letter names and such.
chdir() understands the concept of a per-drive current working
directory, and the "currently logged drive". Check this out:
4> (chdir "f:") ;; basically a bare interface to the chdir syscall
t
5> (pwd) ;; wrapper for getcwd
"F:/"
6> (chdir "c:")
t
7> (pwd)
"C:/Users/kaz"
8>
If you want a program ported to Windows via Cygwin to understand native
conventions, Cygnal goes a long way.
--
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:[~2019-07-27 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 18:27 Kaz Kylheku [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-26 17:12 Soegtrop, Michael
2019-07-26 18:15 ` Ken Brown
2019-07-26 20:03 ` Kaz Kylheku
2019-07-26 20:08 ` Soegtrop, Michael
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=23a9789b9880e266b34f92c2728cdfa4@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).