Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "'Robert Collins'" <robert DOT collins AT itdomain DOT com DOT au>,
   "'Charles Wilson'" <cwilson AT ece DOT gatech DOT edu>,
   "'Jan Nieuwenhuizen'" <janneke AT gnu DOT org>
Cc: <cygwin AT cygwin DOT com>
Subject: RE: missing file FOO.dll
Date: Sat, 1 Jun 2002 02:06:57 +1000
Message-ID: <000c01c208bd$30ad2550$0200a8c0@lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <000701c208bc$c3346560$0200a8c0@lifelesswks>
X-OriginalArrivalTime: 31 May 2002 16:06:57.0576 (UTC) FILETIME=[30868A80:01C208BD]



> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Robert Collins

>  
> > As I explained, XEmacs doesn't HAVE a setup.hint.
> 
> XEmacs uses a fork of setup. Someone who cares might like to suggest
> that they update their fork to a more recent codebase, or ... 
> provide a
> setup.ini for cygwin users.

Or is it the other Emacs. Ah well, I can't remember at this time of
morning. Suffice to say, that there are non-intrusive and easy options
the Xemacs folk can use to get cygwin's setup to install the needed
dependencies automatically.

Rob


--
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/