Summary: | app-misc/tmux-2.1: TERM unset in initial window | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Nerone <mike> |
Component: | Current packages | Assignee: | Alex Alexander (RETIRED) <wired> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | shell-tools |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Nerone
2015-11-14 20:27:22 UTC
I should have said "Gentoo's *lack* of a stock tmux.conf". I only meant to say I had moved out my ~/.tmux.conf to test. Also, I realized I can't be sure prior versions _didn't_ exhibit this problem because my ~/.tmux.conf had some $TERM-affecting customizations that might have inadvertently also acted as a workaround for the misbehavior. Since they don't work around it _now_, though, it does seem likely that this is, in fact, a new problem. Ping? Incidentally, I tried using some different terminals (even plain ole' xterm) to eliminate konsole as a possible cause, and I had the same behavior regardless of terminal software. Well, as I was looking at this again, I realized it was a problem deep inside a startup script. Not tmux's fault at all. |