| 1 |
> | That'd also solve the cases where a terminal changes right beneath a |
| 2 |
> | running application. That |
| 3 |
> | happens during attaching a screen session. |
| 4 |
> |
| 5 |
> No it doesn't. Screen provides a virtual terminal with lots and lots of |
| 6 |
> capabilities. It then reduces them itself internally to what it thinks |
| 7 |
> the underlying term supports -- again, this is done via terminfo, so if |
| 8 |
> you're running screen on xterm you're running a crippled screen. |
| 9 |
|
| 10 |
So, screen advertises the same capabilities to the starting apps regardless the |
| 11 |
terminal the screen is being run on? |
| 12 |
|
| 13 |
Or it advertises reduced capabilities according the terminal it's currently |
| 14 |
attached to? |
| 15 |
|
| 16 |
As for the former, I don't think that would work. If an app chooses a multi |
| 17 |
color style cuz screen is able to handle it, but then screen tries to reduce it |
| 18 |
to mono. |
| 19 |
|
| 20 |
And for the later, it'd work much better if terminal could pump its capabilities |
| 21 |
to the app at runtime, that is during reattachment. Would it be that hard to |
| 22 |
extend window resize or something? |
| 23 |
|
| 24 |
Ivan |
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives