From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: A few Windows build fixes Date: Tue, 06 Sep 2011 23:29:01 -0400 Message-ID: References: <83vcth40ik.fsf@kalahari.s2.org> <83r5444ome.fsf@kalahari.s2.org> <87pqjmfgia.fsf@gmail.com> <8739ggf8ph.fsf@gmail.com> <8262lbu7g5.fsf@gmail.com> <83y5y7cthv.fsf@gnu.org> <83ty8vt4y8.fsf@gnu.org> <83obz2uc11.fsf@gnu.org> <83aaahjzmh.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1315366153 21541 80.91.229.12 (7 Sep 2011 03:29:13 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 7 Sep 2011 03:29:13 +0000 (UTC) Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 07 05:29:09 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R18p3-0008EV-Dh for ged-emacs-devel@m.gmane.org; Wed, 07 Sep 2011 05:29:09 +0200 Original-Received: from localhost ([::1]:42472 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R18p2-00070f-V4 for ged-emacs-devel@m.gmane.org; Tue, 06 Sep 2011 23:29:08 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:51949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R18p0-00070Z-G5 for emacs-devel@gnu.org; Tue, 06 Sep 2011 23:29:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R18oz-0007wS-Jg for emacs-devel@gnu.org; Tue, 06 Sep 2011 23:29:06 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:7851 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R18oy-0007w7-5L; Tue, 06 Sep 2011 23:29:04 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EANXkZk64rwMJ/2dsb2JhbABDqAt5gUYBAQQBViMQCzQSFBgNEAETiAi3D4ZrBKAehEA X-IronPort-AV: E=Sophos;i="4.68,343,1312171200"; d="scan'208";a="134865953" Original-Received: from 184-175-3-9.dsl.teksavvy.com (HELO ceviche.home) ([184.175.3.9]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 06 Sep 2011 23:29:01 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 8576B66246; Tue, 6 Sep 2011 23:29:01 -0400 (EDT) In-Reply-To: <83aaahjzmh.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Sep 2011 21:26:46 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.183 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:143789 Archived-At: >> > Yes, we do: on the lowest possible level that Emacs handles file names >> > before it passes them to system APIs. I pointed out the relevant >> > function in w32.c where that happens. If you transform all file names >> > there, every single feature of Emacs will work as expected by users. >> You're talking about adding support for cygwin file names at the very >> lowest level? > I'm saying that this is the only way to have reliable support for > Cygwin file names (as opposed to something that only "mostly" works). >> We'd want it to have zero impact to the users who don't use cygwin >> (and may not even have it installed), of course. > They will never see such file names. That can be argued (all file names starting with "/" are potential Cygwin names). But the issue I was referring to is that we want the Emacs executable to work even if Cygwin is not available, so either we have to re-implement the Cygwin file-name translation (as is partly done in cygwin-mount) or we have to dyn-load the Cygwin run-time when available. >> Also, once cygwin file names are supported, I think people will expect >> more integration of (native) Emacs and cygwin, e.g. in subprocesses. > What problems are there with Cygwin subprocesses? Emacs already > recognizes Cygwin executables and adapts itself, at least to some > extent (quoting of command-line arguments). I thought we still had problems delivering signals to them. If not, great. Stefan