Timeline for Losing color when starting screen session
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18 at 11:42 | comment | added | Marcus Müller | Hey JdeBP, I just went ahead and added -T usage info to your answer; it seems you might have wanted to do that yourself. | |
| Mar 18 at 11:39 | history | edited | Marcus Müller | CC BY-SA 4.0 | added 166 characters in body |
| Jun 11, 2018 at 16:35 | vote | accept | ProdIssue | ||
| May 15, 2018 at 13:30 | comment | added | ProdIssue | I think there is some kind of limitation on this host. When I login to an ubuntu host start a screen session there and then have each terminal login to the problem host things work fine, I suppose because I am using the settings of the original host. | |
| May 15, 2018 at 13:21 | comment | added | ProdIssue | I tried screen defbce/bce on however the exec defbce or bce does not exist on the host. Also setting the TERM variable to one of the ones you suggested in and out of the screen session did not fix the issue. | |
| May 15, 2018 at 13:19 | vote | accept | ProdIssue | ||
| May 15, 2018 at 13:20 | |||||
| May 14, 2018 at 21:00 | comment | added | Thomas Dickey | In either case, the explanation of why there's no color appears to be missing. | |
| May 14, 2018 at 20:55 | comment | added | JdeBP | It would, as its actual processing of SGR sequences is unaffected by the environment variable in some other process. The version of Screen that wouldn't support more than that would be one dating from before the introduction (into Screen) of 8-bit indexed colour support. I haven't checked when that was, because (as I said) it isn't the very likely case. (-: | |
| May 14, 2018 at 20:49 | comment | added | Thomas Dickey | screen honors the 256-color escapes in either case (checked an hour ago). | |
| May 14, 2018 at 20:40 | history | answered | JdeBP | CC BY-SA 4.0 |