[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how paths work in cygwin?

From: Eli Zaretskii
Subject: Re: how paths work in cygwin?
Date: Mon, 18 Jan 2016 17:52:43 +0200

> From: Leo Liu <address@hidden>
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]