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 19:48:11 +0300 Message-ID: <83ehzs70z8.fsf@gnu.org> 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 1315414159 15898 80.91.229.12 (7 Sep 2011 16:49:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 7 Sep 2011 16:49:19 +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 18:49:07 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 1R1LJ9-0003B1-Ik for ged-emacs-devel@m.gmane.org; Wed, 07 Sep 2011 18:49:03 +0200 Original-Received: from localhost ([::1]:33706 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1LJ8-0002d1-T2 for ged-emacs-devel@m.gmane.org; Wed, 07 Sep 2011 12:49:02 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1LJ5-0002cf-Vk for emacs-devel@gnu.org; Wed, 07 Sep 2011 12:49:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R1LJ4-0000cD-AC for emacs-devel@gnu.org; Wed, 07 Sep 2011 12:48:59 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:51519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1LJ4-0000c0-3f for emacs-devel@gnu.org; Wed, 07 Sep 2011 12:48:58 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LR500A00VZ4E500@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Wed, 07 Sep 2011 19:48:07 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.126.9.62]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LR500906W06OGE0@a-mtaout20.012.net.il>; Wed, 07 Sep 2011 19:48:07 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.166 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:143795 Archived-At: > From: Stefan Monnier > Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org > Date: Wed, 07 Sep 2011 08:50:37 -0400 > > > 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". > > FWIW, in that example, the mount point was "/some/where is mounted on /" > (and as it turns out the "mounted on /" is a case not handled by > cygwin-mount.el). So /home/foo really meant /some/where/home/foo, but > to figure that out, we'd first have to decide whether to interpret > /home/foo as a Cygwin name or as a native name. File names on Emacs seldom come as "/foo/bar" without a drive letter. So we can guess these names are Cygwin names. But even if we don't want to guess, checking for existent of a directory that is directly under / is very fast, even on Windows. So we could check that always, and probably need a user variable to turn that off (for users who, like me, will never install Cygwin). > >> 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. > > It is a cause of problems for the SSL/TLS support (when we use > gnutls-cli rather than the gnutls DLL), for example. If someone writes code to deliver signals to Cygwin processes, I'm sure we will accept the patches. I know nothing about that except that it uses some Cygwin-specific magic.