[haiku-development] Re: Fwd: [haiku-bugs] Re: [Haiku] #9636: Error opening terminal: xterm-256color

  • From: Christoph Thompson <cjsthompson@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 8 Apr 2013 12:26:32 +0200

Hi,

I can confirm that there's no package on Linux that still uses libtermcap.
Everything uses ncurses nowadays.



On Mon, Apr 8, 2013 at 8:43 AM, Siarzhuk Zharski <zharik@xxxxxx> wrote:

> Hi All,
>
> I repost it here, just to explain about reasons of my decision to wide
> audience.
>
> #9636: Error opening terminal: xterm-256color
> ------------------------------**-------+----------------------**------
>    Reporter:  humdinger              |      Owner:  siarzhuk
>        Type:  bug                    |     Status:  closed
>    Priority:  normal                 |  Milestone:  R1
>   Component:  Applications/Terminal  |    Version:  R1/Development
>  Resolution:  no change required     |   Keywords:  xterm, nano
>  Blocked By:                         |   Blocking:
> Has a Patch:  0                      |   Platform:  All
> ------------------------------**-------+----------------------**------
> Ticket URL: 
> <http://dev.haiku-os.org/**ticket/9636#comment:4<http://dev.haiku-os.org/ticket/9636#comment:4>
> >
>
> Comment (by siarzhuk):
>
>  Replying to [comment:3 bonefish]:
>  > TBH, I don't understand why we're setting `TERM` to "xterm-256color".
>
>  Because "xterm" has Co (color count) set to 8. So to let the newest
>  versions of console apps (text editors for example) profit from our 256
>  colors support out of the box - I have switched to xterm-256color and
>  fixed the Terminal BCE processing.
>
>  > Back in the day when I changed it from "beterm" or what it originally
>  was to "xterm" I did that exactly to avoid those compatibility issues.
>
>  Yes, from the same reason I have rejected any patches that have proposed
>  to introduce the "haiku" terminal entry.
>
>  > The whole termcap system is broken by design
>
>  Let me to not agree here - it is just outdated nowadays. libtermcap that
>  we are using is looking like abandoned at the moment. But you are right
>  that termcap format is restricted.
>
>  > and IMO we should just go the path of the least resistance and set
>  `TERM` to "xterm".
>
>  I suspect that console applications do not disappear for the nearest
>  decade so we have to take care about them anyway. IMO, the only reasonable
>  way to keep this sub-system up to date - is switching from termcap to
>  terminfo that is more flexible and maintained as part of ncurses package.
>  More ideas and arguments are here: 
> //www.freelists.org/post/**haiku-<//www.freelists.org/post/haiku->
>  development/What-to-do-with-**termcap
>
>  > To my knowledge that's what pretty much every OS and distribution that
>  matters does as well.
>
>  Corresponding to Thomas E. Dickey: http://invisible-
>  
> island.net/ncurses/ncurses.**faq.html<http://island.net/ncurses/ncurses.faq.html>
>
>  {{{
>  "Additionally, Mac OS X 10.7 is reported to use xterm-256color as a
>  default $TERM value."
>  }}}
>
>  So looks like I'm not alone who think this way.
>
> --
> Kind Regards,
>    S.Zharski
>
>

Other related posts: