Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <1279.192.168.0.7.1119668992.squirrel@waveform.plus.com>
Date: Sat, 25 Jun 2005 04:09:52 +0100 (BST)
Subject: Re: More robust color terminal
From: "Dave Hughes" <dave AT waveform DOT plus DOT com>
To: cygwin AT cygwin DOT com
User-Agent: SquirrelMail/1.4.4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
References: <42BAF439 DOT 6060403 AT cornell DOT edu>        <Pine DOT GSO DOT 4 DOT 61 DOT 0506241030050 DOT 18240 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.61.0506241030050.18240@slinky.cs.nyu.edu>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j5P383pg006784

On Fri, June 24, 2005 15:45, Igor Pechtchanski said:
> On Thu, 23 Jun 2005, Laran Evans wrote:
[snip]
>> Any suggestions?
>
> Both rxvt and the cmd.exe window only support 16 colors.  I guess you
could run X and use an xterm (which should support 256 colors, IIRC).
>
> Alternatively, you could compile (and, hopefully, contribute) gvim. :-)

I vaguely recall trying to build gvim on Cygwin some time ago (and
failing) but, as Reid Thompson pointed out elsewhere in this thread, gvim
builds OOTB now. I've just tried this and it works like a charm (no
special configure switches or anything, just a straight pull from CVS of
the latest source, hit make and let it go)! Spent an hour hacking around
some Python in gvim (GTK GUI) under Cygwin and found not one single
problem. Very nice :-)

Hopefully I'm not rushing headlong into this, but I've just skimmed
through the Package Contributor's Guide and I think I might be able to put
together a package for gvim (and, if building it stays this easy, maintain
it). A few thoughts occurred though, and I just wanted to check I'm not
completely mad (which is a distinct possibility at this time of the
morning):

I can understand the rationale behind wanting to package gvim separately
to vim (allows for people who want vim, but don't want X). However,
they're basically the same app. Would it make sense for a gvim package to
include just the gvim binary, and have a dependency on the main vim
package to provide the runtime files (syntax highlighting configs and such
like)?

If that's the case, it also sounds like the gvim package wouldn't include
a src package but would use the external-source directive in the
setup.hint to point at the vim package's sources. Or am I talking crazy talk?

Anyway, I'll have a look at the natty package build-script tomorrow and
see if I can't come up with something ... but right now I've got to catch
up on a week of sleep deprivation :-)

-- 
Dave Hughes



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/