From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: how paths work in cygwin? Date: Mon, 18 Jan 2016 17:52:43 +0200 Message-ID: <83d1syevg4.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453132383 20606 80.91.229.3 (18 Jan 2016 15:53:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jan 2016 15:53:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Leo Liu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 18 16:52:56 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aLC6y-0004vm-32 for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 16:52:56 +0100 Original-Received: from localhost ([::1]:60406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC6x-0003wo-KT for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 10:52:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC6i-0003we-Re for emacs-devel@gnu.org; Mon, 18 Jan 2016 10:52:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLC6f-00020j-M8 for emacs-devel@gnu.org; Mon, 18 Jan 2016 10:52:40 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC6f-00020f-Ic; Mon, 18 Jan 2016 10:52:37 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1241 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aLC6e-0000rx-UR; Mon, 18 Jan 2016 10:52:37 -0500 In-reply-to: (message from Leo Liu on Mon, 18 Jan 2016 16:24:37 +0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198254 Archived-At: > From: Leo Liu > 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.