From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: how paths work in cygwin?
Date: Mon, 18 Jan 2016 17:52:43 +0200 [thread overview]
Message-ID: <83d1syevg4.fsf@gnu.org> (raw)
In-Reply-To: <m2vb6rxpkq.fsf@gmail.com> (message from Leo Liu on Mon, 18 Jan 2016 16:24:37 +0800)
> From: Leo Liu <sdl.web@gmail.com>
> Date: Mon, 18 Jan 2016 16:24:37 +0800
>
> I am getting a bug report https://github.com/leoliu/ggtags/issues/121
> because emacs and global represent paths in cygwin differently?
>
> global: "/e/gtk-3-compilation/build/gtk+-3.19.4/gtk/"
> emacs: "e:/gtk-3-compilation/build/gtk+-3.19.4/gtk/"
>
> Which path representation is more correct?
Neither, AFAIK. Cygwin file names look like /cygdrive/e/gtk-3-...
What you show looks like MSYS format, not Cygwin format. This is
consistent with what the OP says about invoking 'global' in
"mingw32.exe window".
In sum, I think the OP should use a consistent set of tools, instead
of mixing subtly incompatible sets. My guess is that his 'global' is
an MSYS application or script, not a native Windows port, whereas his
Emacs is a native build. These don't mix too well.
We have the unmsys--file-name function which might help, but I see no
reason why you as a maintainer will need to get into that.
next prev parent reply other threads:[~2016-01-18 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 8:24 how paths work in cygwin? Leo Liu
2016-01-18 15:10 ` Filipp Gunbin
2016-01-19 2:33 ` Leo Liu
2016-01-18 15:52 ` Eli Zaretskii [this message]
2016-01-18 19:01 ` Achim Gratz
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d1syevg4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).