Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 23 Jul 2001 15:24:27 -0400 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: Text editors under Cygnus Message-ID: <20010723152427.C1680@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <4 DOT 3 DOT 1 DOT 2 DOT 20010723140618 DOT 0221ff18 AT pop DOT ma DOT ultranet DOT com> <3B5C6B7E DOT 2050602 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B5C6B7E.2050602@ece.gatech.edu>; from cwilson@ece.gatech.edu on Mon, Jul 23, 2001 at 02:22:54PM -0400 On Mon, Jul 23, 2001 at 02:22:54PM -0400, Charles Wilson wrote: >Larry Hall (RFK Partners, Inc) wrote: > > >> And I'll just follow-up on Chuck's comment by pointing out that XEmacs, >> because it can be built on Cygwin, automatically understands all the >> niceties of the Cygwin environment (like mounts, symlinks, etc) by >> default. > >Bad Larry. No cookie. I said no emacs partisanship flamewar. > >However, you DO have to be honest. While in cygwin-xemacs-21.4.3, the >^x-^f file open command (where you type in the name of the file to open >in the minibuffer) works with cygwin-style paths, the 'Open' toolbar >button does NOT. The toolbar button activates the windows DLL-based >'File Open' dialog, even in the cygwin build. Since that dialog comes >from the windows system libs (comctl.dll? I dunno) it does not and >cannot understand cygwin-style paths. > >That little discrepancy is rather disconcerting, even to a long-time >XEmacs user like me. The older cygwin-xemacs-21.1.13 package works >'cygwin-style' both in the (custom built) file-open dialog and in the >minibuffer. I don't know why the change was made in 21.4.x -- probably >an mswin-related improvement that bled over to cygwin. It didn't bother >me enough to complain (or code) about it. That's interesting. I believe that Insight has/had/will-have/may-have a similar problem. cgf -- 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/