Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3CC6E88C.4080402@ece.gatech.edu>
Date: Wed, 24 Apr 2002 13:17:00 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
MIME-Version: 1.0
To: "B. Joshua Rosen" <bjrosen@polybus.com>
CC: cygwin@cygwin.com
Subject: Re: Cygwin newbie needs help
References: <80575AFA5F0DD31197CE00805F650D767B21EC@wilber.adroit.com> <1019664383.2991.70.camel@saratoga>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

News from XEmacs land:

1) there are two "windows" ports of XEmacs: a fully native port, and a 
cygwin port.

2) Both of these ports use so-called "native windowing": that is, they 
use MSWindows GDI calls to paint their display.  Neither port uses X; 
they cannot be redirected (graphically) thru the network to display 
remotely.

3) If you want that capability, you can only do so with the cygwin build 
-- but you'll have to build it yourself.  Also, the 
cygwin-with-X-windowing build has not been widely used (or tested).  It 
may have suffered bitrot.

4) I *believe* that both the native port and the cygwin port support the 
'-nw' flag, which allows you to use XEmacs in a tty.  Therefore, it is 
probably possible, with the prebuilt native or cygwin versions of 
xemacs, to ssh in to your windows box, and use 'xemacs -nw' to edit 
files.  (Of course, you need a working cygwin ssh daemon running on your 
windows box, but that's a whole 'nother topic.)

--Chuck


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