Re: [screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Thomas Dickey
- Original Message - | From: "Amadeusz Sławiński" | To: "Marcin Cieslak" | Cc: "Screen development" , "Thomas E. Dickey" , | scr...@uni-erlangen.de | Sent: Saturday, November 10, 2018 4:50:43 PM | Subject: Re: [screen-devel] [bug #54989] incorrect use of tparm | On Sat, 10 Nov 2018 21:2

[screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Thomas Dickey
Follow-up Comment #4, bug #54989 (project screen): ncurses 6.1 (like ncurses 6.0) can be compiled to match the feature-set of older releases. Packagers tend to match the older releases... You have to use the "-x" option of infocmp to see extended capabilities, e.g., infocmp -x xterm-direct |gre

[screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Thomas Dickey
Follow-up Comment #5, bug #54989 (project screen): Regarding "xterm-direct", you might find its mention in this page helpful, since it explains why I chose to implement it as is: https://invisible-island.net/ncurses/ncurses-slang.html ___

Re: [screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Amadeusz Sławiński
On Sat, 10 Nov 2018 21:22:22 + Marcin Cieslak wrote: > On Sat, 10 Nov 2018, Amadeusz Sławiński wrote: > > > Still 'infocmp xterm-direct|grep -i rgb' returns nothing, should I be > > checking > > colors# (D_CCO == 32767 check in code above) and pairs#, or am I > > misunderstaning something?

[screen-devel] [bug #54458] Session name length causes problem to "reopen fifo"

2018-11-10 Thread Amadeusz Sławiński
Update of bug #54458 (project screen): Status:None => Confirmed ___ Follow-up Comment #2: Hm... interesting, so it seems that sockaddr_un that is used in MakeServerSocket can only hold 10

Re: [screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Marcin Cieslak
On Sat, 10 Nov 2018, Amadeusz Sławiński wrote: > Still 'infocmp xterm-direct|grep -i rgb' returns nothing, should I be checking > colors# (D_CCO == 32767 check in code above) and pairs#, or am I > misunderstaning something? >From what I understand there is no true color support in termcap/terminf

[screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Amadeusz Sławiński
Follow-up Comment #3, bug #54989 (project screen): I guess this will simplify things a bit, but will probably require some more work than just that: - if (f != of && (f & 0x0400) && hastruecolor) { - uint8_t _r, _g, _b; - - _r = (f & 0x00ff) >> 16; -

[screen-devel] [bug #54556] screen is producing invalid TERMCAPs

2018-11-10 Thread Thomas Dickey
Follow-up Comment #1, bug #54556 (project screen): Pasting that into a file, the result looks ok and "tic -c" finds no problem. Line 20 seems to be this: :F7=\E[15;2~:F8=\E[17;2~:F9=\E[18;2~:FA=\E[19;2~:\ however the error message seems to say that there's some point in the actual string where

[screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Thomas Dickey
Follow-up Comment #2, bug #54989 (project screen): ncurses 6.1 supports direct color by allowing 32-bit numbers in terminal descriptions, and adds an extended capability RGB which tells if/how the color number maps to red/green/blue components. The RGB capability is only provided via the terminfo

Re: [screen-devel] None of the commands work?

2018-11-10 Thread Amadeusz Sławiński
On Wed, 31 Oct 2018 12:53:51 + ledgerq wrote: > Hey > I'm very new to screen and was super happy to use it but for some reason none > of the navigation keys work anymore? > starting with ctrl a + c ?? > when I type screen in terminal it starts the usual message and at the end it > wont let

[screen-devel] [bug #54989] incorrect use of tparm

2018-11-10 Thread Amadeusz Sławiński
Follow-up Comment #1, bug #54989 (project screen): Yes, I'm aware of the problem. Proposed fix seems to work ok in my tests. But as mentioned it would be better if we could just get escape code from parent terminal terminfo. There seemed to be some work in this area to expose this information, b