public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Thu, 29 Jan 2009 17:07:00 -0000	[thread overview]
Message-ID: <hqh3o4lgioltfcodnhrm4e44m6btpjclcc@4ax.com> (raw)
In-Reply-To: <loom.20090128T064317-555@post.gmane.org>

> I'm using a Perl script, available at
> http://www.frexx.de/xterm-256-notes/data/256colors2.pl, to test whether my
> terminal is giving me 256 colors.

Thanks, this is helpful.

>  It works when I run it from a vanilla bash
> prompt, but not from within Screen, even after I installed your build.

OK.  Same here.  I get a variety of different results with different
combinations of Cygwin version (1.5, 1.7), terminal type (DOS, xterm) and
with/without screen.  Without modification, the only combination that gives 256
colors for me is Cygwin 1.5, xterm, without screen.  All others give 8 colors,
and the colormap is garbled in the DOS terminals (big surprise).

However, in /usr/share/terminfo/s, there is a variety of screen* files,
including several named screen-256color*.  So it turns out that for me, running

TERM=screen-256color screen

gives 256 colors, at least in Cygwin 1.5.  Can you confirm this?

In Cygwin 1.7, I still only get 8 colors.  I'll report that separately as a bug.

Andrew.


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

  reply	other threads:[~2009-01-29 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  9:57 Justin L.
2009-01-26 22:33 ` Andrew Schulman
2009-01-27  3:19   ` Justin L.
2009-01-28  2:08     ` Andrew Schulman
2009-01-28 10:19       ` Justin L.
2009-01-29 17:07         ` Andrew Schulman [this message]
2009-01-29 20:28           ` Justin L.
2009-01-29 22:54             ` Andrew Schulman
2009-01-30  9:34               ` Justin L.
2009-01-30 13:02                 ` Andrew Schulman
2009-02-19 16:09               ` Presto Ten
2009-02-19 16:27                 ` Andrew Schulman
2009-02-19 17:55                   ` Matt Wozniski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=hqh3o4lgioltfcodnhrm4e44m6btpjclcc@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).