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: A few Windows build fixes Date: Wed, 07 Sep 2011 01:17:56 -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> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1315372690 26956 80.91.229.12 (7 Sep 2011 05:18:10 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 7 Sep 2011 05:18:10 +0000 (UTC) Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 07 07:18:03 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 1R1AWP-0001jI-6D for ged-emacs-devel@m.gmane.org; Wed, 07 Sep 2011 07:18:02 +0200 Original-Received: from localhost ([::1]:58891 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1AWO-0002yt-KO for ged-emacs-devel@m.gmane.org; Wed, 07 Sep 2011 01:18:00 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1AWM-0002yd-Ra for emacs-devel@gnu.org; Wed, 07 Sep 2011 01:17:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R1AWL-0003RK-Fc for emacs-devel@gnu.org; Wed, 07 Sep 2011 01:17:58 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:35836) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1AWL-0003RG-E3 for emacs-devel@gnu.org; Wed, 07 Sep 2011 01:17:57 -0400 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1R1AWK-0008Cp-Rn; Wed, 07 Sep 2011 01:17:56 -0400 In-reply-to: (message from Stefan Monnier on Tue, 06 Sep 2011 23:29:01 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:143790 Archived-At: > From: Stefan Monnier > Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org > Date: Tue, 06 Sep 2011 23:29:01 -0400 > > >> 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). I was talking about /cygdrive/x/ file names that should be translated to x:/ and vice versa. This must be on the C level, AFAIU. The "mounted" file names, if we want or need to support them, will have to be looked up in the mount list taken from "mount -m". But I'm not sure we need this, as /cygdrive/x/ should be sufficient. However, I don't use Cygwin, so maybe I'm missing some important use cases that do need this. > 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. I don't see how the fact that Cygwin is or isn't installed is related to implementing the translation, except that "mount -m" will fail if Cygwin is not installed. We can use this failure to disable translation, or we can translate /cygdrive/x/ anyway, because it is unlikely that a random w32 user will have a real /cygdrive/x/ directory on her disk. Loading the Cygwin DLL into a native w32 process is impossible, so that's not an option. > I thought we still had problems delivering signals to them. You are right, we don't support sending Posix signals to Cygwin programs. But where is that a real problem? Emacs does know how to interrupt a subprocess, and the way it does that should work with Cygwin programs as well, albeit with less flexibility. After all, Cygwin programs are just specialized Windows applications.