public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Matt Wozniski <godlygeek@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Thu, 19 Feb 2009 17:55:00 -0000	[thread overview]
Message-ID: <17393e3e0902190955k58d359act76cb364965968fcf@mail.gmail.com> (raw)
In-Reply-To: <922rp452nq682lcpobk7gbukuu1glcuai9@4ax.com>

On 2/19/09, Andrew Schulman wrote:
> > 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))
>
>
> Thanks, this is good to know.  I'll include it in the screen.README.

Having xterm set TERM=xterm-256color and screen set
TERM=screen-256color makes vim's high color support work fine with no
extra configuration required.

~Matt

--
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-02-19 17:55 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
2009-02-19 16:27                 ` Andrew Schulman
2009-02-19 17:55                   ` Matt Wozniski [this message]

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=17393e3e0902190955k58d359act76cb364965968fcf@mail.gmail.com \
    --to=godlygeek@gmail.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).