On 2014-09-09 Egmont Koblinger wrote: > You can compare the environment of the "correct" and "incorrect" mc > inside screen (e.g. in case of Linux, by something like tr '\0' '\n' > < /proc/xxx/environ | sort... and then diff).
> Look for TERM, COLORTERM, TERMCAP... who knows what else. Now, I pinned it down. The variable TERMCAP needs to be unset. I now start mc via a screen hotkey like this: bind C screen -t 'mc' env TERMCAP= mc -x and everything is okay. I don't really understand it because I did not set any TERMCAP variable before, nor did I have any "termcapinfo" stanzas in my .screnrc. Could this be something worth mentioning in a faq, or is it possibly some error on my part that I have now corrected in a clumsy fashion? Thanks, Morten > On Tue, Sep 9, 2014 at 2:54 PM, Morten Bo Johansen <m...@spamcop.net> wrote: >> On 2014-09-09 Yury V. Zaytsev wrote: >>> On Tue, 2014-09-09 at 14:31 +0200, Egmont Koblinger wrote: >>>> I'm not familiar enough with screen to help you beyond this point. It >>>> doesn't properly set $TERM, but I don't know how to make it set it. >>> Maybe something horrible like >>> bind C screen -t 'mc' TERM=screen-256color mc -x >> I tried: >> bind C screen -t 'mc' env TERM=screen-256color mc -x >> but no cigar. >> Thanks, >> Morten >> _______________________________________________ >> mc-devel mailing list >> https://mail.gnome.org/mailman/listinfo/mc-devel > _______________________________________________ > mc-devel mailing list > https://mail.gnome.org/mailman/listinfo/mc-devel _______________________________________________ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
