From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107814 invoked by alias); 26 Jul 2019 17:12:06 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 107807 invoked by uid 89); 26 Jul 2019 17:12:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_50,HTML_MESSAGE autolearn=ham version=3.3.1 spammy=ancient, chairperson, 10-12, Chairperson X-HELO: mga18.intel.com Received: from mga18.intel.com (HELO mga18.intel.com) (134.134.136.126) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 Jul 2019 17:12:02 +0000 Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jul 2019 10:12:00 -0700 Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga004.fm.intel.com with ESMTP; 26 Jul 2019 10:11:59 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.59]) by IRSMSX108.ger.corp.intel.com ([169.254.11.229]) with mapi id 14.03.0439.000; Fri, 26 Jul 2019 18:11:58 +0100 From: "Soegtrop, Michael" To: "cygwin@cygwin.com" Subject: Interest in Emacs patched to handle Windows paths? Date: Fri, 26 Jul 2019 17:12:00 -0000 Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FDB3DF2@IRSMSX102.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-07/txt/msg00225.txt.bz2 Dear Cygwin Team and Users, In May I modified Emacs for Cygwin so that it can truly handle Windows path= s. I do a lot of MinGW cross compilation on Windows and want to seamlessly = use tools like debuggers compiled for MinGW in Cygwin Emacs, so I need this= . I also tried the Windows Emacs distrubution, but it didn't find it very c= onvincing, because it comes with yet another Posix layer for Windows, and a= rather heavy one. Cygwin Emacs is a substantially more elegant solution. O= ne can find some emacs lisp packages to help with this, but they all rely o= n path translation, so an open works but the path Emacs uses internally is = the Cygwin path then. This is in many cases not good enough. I found that I= have to modify the core C file handling file (src/fileio.c) to make it rea= lly work. I wanted to ask if there is general interest in this. If so I would like to= publish this work. But to do so I would need some advice on how to do this= . The path handling code of Emacs is localized (src/fileio.c) but quite obs= cure and I would even call it messy so it requires quite a few changes and = it is hard to tell if my changes to support Posix and Windows paths in one = build don't break compatibility with some ancient operating systems. For th= is reason it might be hard to get these changes into Emacs upstream, so tha= t this would just be a compile time option. The alternatives would be to have a separate package in Cygwin which applie= s a patch to emacs, say an emacs-winpath package I could maintain. Of cause= I would try to get it upstream to reduce maintenance effort, but as I said= , it might get tricky because I don't have access to a computer museum to t= est Emacs on all platforms it supports. Please let me know your thoughts on this. Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple