Opened 14 years ago
Closed 12 years ago
#6424 closed enhancement (fixed)
Vim not displaying color unless TERM is set to "xterm-color"
Reported by: | ali3n0 | Owned by: | siarzhuk |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Command Line Tools | Version: | R1/alpha2 |
Keywords: | vim bash terminfo color xterm | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
To make vim display colored syntax highlighting seems there's no other way to force the TERM environment to "xterm-color" value. As a workaround, adding "export TERM=xterm-color" in /boot/home/config/boot/UserSetupEnvironment works, but, if there are no reasons to keep it as it is, TERM could default to "xterm-color" instead of "xterm"
Change History (7)
follow-up: 2 comment:1 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
Replying to axeld:
As I just mentioned on the mailing list, in Linux it works just fine with TERM=xterm, so this is an issue of the vim port, not of Haiku.
I'm inclined to blame the ncurses/termcap which ships with Haiku. vim works fine for me with TERM=xterm if I have a terminfo database installed.
comment:3 by , 14 years ago
Keywords: | terminfo added; term removed |
---|---|
Resolution: | invalid |
Status: | closed → reopened |
Now that's important information, thanks!
comment:4 by , 14 years ago
I think it's a good time to remove ncurses from our repository and make it (mandatory) optional package.
comment:5 by , 14 years ago
No matter what I set TERM to, curses-based remote applications over telnet and SSH get horribly deformed - in almost the exact same way as using the version of Microsoft Telnet that comes with XP. I also saw the same behavior with vim and xterm vs. xterm-color with the latest nightly (hrev40312 gcc2-hybrid). I'd say Haiku's ncurses is in dire need of a fix.
comment:6 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | reopened → assigned |
As I just mentioned on the mailing list, in Linux it works just fine with TERM=xterm, so this is an issue of the vim port, not of Haiku.