From: Presto Ten <presto08@me.com>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Thu, 19 Feb 2009 16:09:00 -0000 [thread overview]
Message-ID: <22103799.post@talk.nabble.com> (raw)
In-Reply-To: <l634o49gg4feoe37afo2lllqh7nio79j8p@4ax.com>
Andrew Schulman-3 wrote:
>
>> screen-256color: GNU Screen compiled with the --enable-colors256 flag;
>> without
>> this flag, terminals launched from within Screen can only show 16 colors.
>> Depending on your terminal, you may need to launch Screen as
>> 'TERM=screen-256color screen' in order for 256 colors to work.
>
> OK, thanks. I'll put a new release out soon with 256 colors enabled, at
> least
> for Cygwin 1.5.
>
> I'm curious: where do you use this? I've been using 8 or 16 colors I
> guess,
> for all of this time and never noticed it. I don't colorize my ls output,
> for
> example, as I know many people do. If there's a common application for
> this, it
> would help to point it out to users.
>
Great that this will be included in an official Cygwin screen package! The
256 colors mode is invaluable for people using Emacs in terminal mode: Emacs
supports 256 colors, and code becomes a lot easier on the eye.
By the way, I downloaded
http://home.comcast.net/~andrex2/cygwin-1.5/screen/screen-4.0.3-3.tar.bz2
and tried it on Cygwin 1.5 with PuTTY (256 colors enabled): started screen
plus Emacs, and it shows all 256 colors with M-x list-colors-display!
Beautiful.
Note that for Emacs to recognize screen-256color, you need to add the
following into "term/screen-256color.el" in the load path (for Emacs 22):
(defun terminal-init-screen ()
"Terminal initialization function for screen."
;; Use the xterm color initialization code.
(load "term/xterm")
(xterm-register-default-colors)
(tty-set-up-initial-frame-faces))
-p
--
View this message in context: http://www.nabble.com/Can%27t-compile-Screen%3A-Undefined-reference-to-__imp__ospeed-tp21660755p22103799.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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/
next prev parent reply other threads:[~2009-02-19 16:09 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
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 [this message]
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=22103799.post@talk.nabble.com \
--to=presto08@me.com \
--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).