X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_66,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <922rp452nq682lcpobk7gbukuu1glcuai9@4ax.com> References: <22103799.post@talk.nabble.com> <922rp452nq682lcpobk7gbukuu1glcuai9@4ax.com> Date: Thu, 19 Feb 2009 12:55:22 -0500 Message-ID: <17393e3e0902190955k58d359act76cb364965968fcf@mail.gmail.com> Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed From: Matt Wozniski To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/