3 ms·

I'm not sure if it's a version, terminal, or configuration issue, but htop works fine in tmux for all of my shells...

inetknght 7y ago
I'm pretty sure it's a version + terminal + configuration issue. I work in terminals all day long at home and work. I have a consistent user profile. On the other hand different operating systems have different terminals. I've seen the symptom occur locally (Ubuntu -> Gnome-Terminal -> bash -> tmux) and usually go away after an update of one of the components. But most frequently it occurs when crossing boundaries ({Windows, Fedora, Ubuntu} | {putty,gnome-terminal,tilix,serial tty} | tmux | literally anything). It happens more frequently when embedding tmux sessions while crossing those boundaries. I _really_ wish there existed some software which would try to debug terminal display issues, even if it involved echoing something in a client program and then asking me "does this show up as intended and/or garbled?", with a timeout value for "it's so garbled that the user couldn't read or respond" similar to configuring a video display.
- lloeki 7y ago
  This looks like some typical TERM env var/termcap mismatch with reality.
  - inetknght 7y ago
    All the terminal emulators support xterm-256color and that's what the TERM is set to outside of tmux. The TERM inside of tmux (and ssh sessions inside tmux and etc) is `tmux-256color` as tmux is documented to want. I just wish I knew how to debug it.
    - JdeBP 7y ago
      No, they do not. And it's this erroneous thinking that causes so many of the problems. * https://invisible-island.net/ncurses/ncurses.faq.html#xterm_generic https://invisible-island.net/ncurses/ncurses.faq.html#xterm_... * http://jdebp.uk./Softwares/nosh/guide/commands/TERM.xml#MIS-CONFIGURATION http://jdebp.uk./Softwares/nosh/guide/commands/TERM.xml#MIS-... * https://unix.stackexchange.com/a/419092/5132 https://unix.stackexchange.com/a/419092/5132 * https://unix.stackexchange.com/a/446912/5132 https://unix.stackexchange.com/a/446912/5132 * https://unix.stackexchange.com/a/515517/5132 https://unix.stackexchange.com/a/515517/5132 * https://unix.stackexchange.com/a/427299/5132 https://unix.stackexchange.com/a/427299/5132 * https://unix.stackexchange.com/a/441899/5132 https://unix.stackexchange.com/a/441899/5132 * https://unix.stackexchange.com/a/560992/5132 https://unix.stackexchange.com/a/560992/5132
      - inetknght 7y ago
        oof today I learned an assumption I made is wildly inaccurate. Thanks, now I need to go re-evaluate my terminal choices luckily it's a weekend

I'm pretty sure it's a version + terminal + configuration issue. I work in terminals all day long at home and work. I have a consistent user profile. On the other hand different operating systems have different terminals. I've seen the symptom occur locally (Ubuntu -> Gnome-Terminal -> bash -> tmux) and usually go away after an update of one of the components. But most frequently it occurs when crossing boundaries ({Windows, Fedora, Ubuntu} | {putty,gnome-terminal,tilix,serial tty} | tmux | literally anything). It happens more frequently when embedding tmux sessions while crossing those boundaries. I _really_ wish there existed some software which would try to debug terminal display issues, even if it involved echoing something in a client program and then asking me "does this show up as intended and/or garbled?", with a timeout value for "it's so garbled that the user couldn't read or respond" similar to configuring a video display.

lloeki 7y ago
This looks like some typical TERM env var/termcap mismatch with reality.
- inetknght 7y ago
  All the terminal emulators support xterm-256color and that's what the TERM is set to outside of tmux. The TERM inside of tmux (and ssh sessions inside tmux and etc) is `tmux-256color` as tmux is documented to want. I just wish I knew how to debug it.
  - JdeBP 7y ago
    No, they do not. And it's this erroneous thinking that causes so many of the problems. * https://invisible-island.net/ncurses/ncurses.faq.html#xterm_generic https://invisible-island.net/ncurses/ncurses.faq.html#xterm_... * http://jdebp.uk./Softwares/nosh/guide/commands/TERM.xml#MIS-CONFIGURATION http://jdebp.uk./Softwares/nosh/guide/commands/TERM.xml#MIS-... * https://unix.stackexchange.com/a/419092/5132 https://unix.stackexchange.com/a/419092/5132 * https://unix.stackexchange.com/a/446912/5132 https://unix.stackexchange.com/a/446912/5132 * https://unix.stackexchange.com/a/515517/5132 https://unix.stackexchange.com/a/515517/5132 * https://unix.stackexchange.com/a/427299/5132 https://unix.stackexchange.com/a/427299/5132 * https://unix.stackexchange.com/a/441899/5132 https://unix.stackexchange.com/a/441899/5132 * https://unix.stackexchange.com/a/560992/5132 https://unix.stackexchange.com/a/560992/5132
    - inetknght 7y ago
      oof today I learned an assumption I made is wildly inaccurate. Thanks, now I need to go re-evaluate my terminal choices luckily it's a weekend