Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 26 Feb 2002 12:06:42 +0200 Message-Id: <200202261006.g1QA6gw30441@unix.simonwiesel.co.il> From: "Ehud Karni" To: "Jari Aalto" , " Eli Zaretskii" Cc: Cygwin AT cygwin DOT com, emacs-devel AT gnu DOT org Subject: Emacs for Cygwin (was: cygwin-mount.el, Using GDB in NTEMACS) In-reply-to: <2561-Sat23Feb2002115725+0200-eliz@is.elta.co.il> (message from Eli Zaretskii on Sat, 23 Feb 2002 11:57:25 +0200) Organization: Mivtach-Simon Insurance agencies Reply-to: ehud AT unix DOT simonwiesel DOT co DOT il X-Mailer: Emacs 21.1.1 rmail (send-msg 1.106) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 7bit Below is Eli Zaretskii mail from 23 Feb 2002. I think that we need a CygEmacs - an emacs that will be compiled with the real Cygwin ported gcc (i.e. without the -mno-cygwin). CygEmacs will have UNIX APIs for I/O (files and sockets), and M$Windows APIs for the display and the keyboard. This is already done (partly) by the Cygwin port of rxvt. If this is too difficult, may be a version of Emacs for Cygwin, that use only the UNIX APIs can be ported. This Emacs version will be used only within Cygwin's windows - Console or rxvt (Emacs in TTY mode) or real display (using Cygwin-Xfree). Any of these version will solve the 2 major issues of using Emacs with Cygwin - 1. The files (names and attributes). 2. Running of sub-shells in Emacs (file is not tty problem). It may solve another problem that bothers me - running a client on the PC to a server on UNIX. Ehud. --------------- Original Eli's mail --------------- > From: letters AT hotpop DOT com (Jari Aalto+mail.emacs) > Date: Sat, 23 Feb 2002 11:29:27 +0200 > > all Windows users continue complaining why Emacs does not help them > to use Cygwin environment more easily. They should complain to Cygwin developers. I asked before, and I'll ask again: did someone try to talk to the Cygwin developers about this issue? Did someone ask them what do they think about supporting Windows file names better, and if so, what did they reply? It strikes me that an important party to this discussion is strangely absent. -- Ehud Karni Tel: +972-3-7966-561 /"\ Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign Insurance agencies (USA) voice mail and X Against HTML Mail http://www.mvs.co.il FAX: 1-815-5509341 / \ mailto:ehud AT unix DOT simonwiesel DOT co DOT il Better Safe Than Sorry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/