On Wed, 28 Oct 2009, Micah Cowan wrote:

> Kamus, I see absolutely nothing in Thomas Dickey's comments that even
> remotely hint at a violation of the Code of Conduct, so maybe you could
> consider dialing your sensitivity down a bit?
>
> Thomas, I think the (previous) "Incomplete" status was due to the
> question as to whether it was still reproducible in recent releases; I
> don't believe it is (I've never seen any of "screen.xterm", "screen
> ..xterm-color" or any other provided on an Ubuntu system, so wouldn't be
> able to produce his setup), and the original poster didn't respond in
> nearly a year, so that's normally grounds for closing the bug as
> "Invalid".

I don't have Ubuntu to compare, but my understanding is that it's largely 
a copy of Debian/testing.  Those entries in Debian/testing would be in the
larger "ncurses-term" package:

/usr/share/terminfo/s/screen.rxvt
/usr/share/terminfo/s/screen.xterm-r6
/usr/share/terminfo/s/screen.mlterm
/usr/share/terminfo/s/screen.xterm-xfree86
/usr/share/terminfo/s/screen.teraterm
/usr/share/terminfo/s/screen.Eterm
/usr/share/terminfo/s/screen.linux
/usr/share/terminfo/s/screen.xterm-new

> FWIW, I'm not sure if Ubuntu's "kbs=\177" value counts as a
> "customization"; that's what screen currently provides in its included
> terminfo description, and I know Ubuntu(/Debian) include code from
> relatively recent development versions.

ncurses's terminfo.src has kbs=^H.

Since (all but a few) terminfo entries come from ncurses in Debian, etc.,
the change is addressed by a packager's patch (customization).  In 
particular, the Debian package for 'screen' does not install any terminfo
data...

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

-- 
Screen missing terminfo entries for 'xterm'
https://bugs.launchpad.net/bugs/190852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to