Bug 473977 - vim incorrectly linked to libtermcap instead of libncurses
Summary: vim incorrectly linked to libtermcap instead of libncurses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: vim
Version: 5.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Karsten Hopp
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-01 17:16 UTC by Tom Sorensen
Modified: 2021-06-29 10:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-22 17:27:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1117 0 normal SHIPPED_LIVE vim bug fix update 2009-06-22 17:27:19 UTC

Description Tom Sorensen 2008-12-01 17:16:57 UTC
Description of problem:

vim is apparently linked to libtermcap instead of libcurses or libncurses (preferable). This causes many vim to have incorrect capabilities under many values for TERM.


Version-Release number of selected component (if applicable):
vim-enhanced-7.0.109-3.el5.3

How reproducible:
100%


Steps to Reproduce:
1. export TERM=putty
2. vim
3. :echo t_Co
  
Actual results:
t_Co=

Expected results:
t_Co=8

Additional info:
If you set TERM=xterm, you get the expected results. Also reproducible for putty-256color vs xterm-256color, and others. :version shows +terminfo but the Linking: section shows -ltermcap. On other platforms (AIX, Solaris) it indicates -lncurses or -lcurses.

This problem is also in RHEL4. I do not have RHEL3 anywhere to check that.

Comment 8 errata-xmlrpc 2009-06-22 17:27:50 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1117.html


Note You need to log in before you can comment on or make changes to this bug.