From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Leo Liu Newsgroups: gmane.emacs.devel Subject: Re: how paths work in cygwin? Date: Tue, 19 Jan 2016 10:33:54 +0800 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1453170880 16575 80.91.229.3 (19 Jan 2016 02:34:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Jan 2016 02:34:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 19 03:34:30 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 1aLM7k-0003hj-O0 for ged-emacs-devel@m.gmane.org; Tue, 19 Jan 2016 03:34:24 +0100 Original-Received: from localhost ([::1]:34581 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLM7j-00078o-V2 for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 21:34:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43935) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLM7X-00078b-54 for emacs-devel@gnu.org; Mon, 18 Jan 2016 21:34:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLM7T-0001l5-V8 for emacs-devel@gnu.org; Mon, 18 Jan 2016 21:34:11 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:39750) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLM7T-0001kN-OH for emacs-devel@gnu.org; Mon, 18 Jan 2016 21:34:07 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aLM7O-0003Y0-4B for emacs-devel@gnu.org; Tue, 19 Jan 2016 03:34:02 +0100 Original-Received: from 116.213.171.151 ([116.213.171.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Jan 2016 03:34:02 +0100 Original-Received: from sdl.web by 116.213.171.151 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Jan 2016 03:34:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 32 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 116.213.171.151 Face: iVBORw0KGgoAAAANSUhEUgAAACgAAAAoAgMAAADxkFD+AAAADFBMVEUvT09qWs3/pQD///+J kUVcAAAAAWJLR0QAiAUdSAAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9cBBwMLOd3veKQA AACuSURBVBjTldE9CgIxEAXgB+lEyFUC2wo5ikdZ8DSypxhMY7H9VuIVwlqkGRgnm59VsHGafIQ3 CZlAtmKIRaHETgYa12lqvEsPYKf8wXHsPGfqPaUM0g9aJPKFXkmNQmSDqwzz4Fpgpz+6WAPY2z5o uPJJpu0uypcl4nyCibMLQ8lCiVjayLoQvw5LsVKQuHPRR958HZbOcVsKeepcLxpByjycGvnKmY+c MBvrtyjfe0vmuLvdq/kAAAAASUVORK5CYII= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (OS X 10.11.2) Cancel-Lock: sha1:HyAJ/mTgLeHlbfWkOl64BuVrGNY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:198330 Archived-At: On 2016-01-18 18:10 +0300, Filipp Gunbin wrote: [snipped 11 lines] > The answer is "use Cygwin port of emacs under Cygwin". > > You could try to support Cygwin paths in Windows Emacs, but I don't know > if that's worth the value. > > There are some path conversion functions in Cygwin Emacs (probably not > in Window Emacs), but they weren't available in the last release I used > on Cygwin. > > Filipp On 2016-01-18 17:52 +0200, Eli Zaretskii wrote: [snipped 12 lines] > 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. Thank you, Filipp and Eli, for the expertise on this. Leo