The problem is that TERM=linux-16color is the terminfo entry that is correct. TERM=linux is the buggy entry, and htop is buggy for using "bold" when it means "bright".
(I can speak with confidence that I am one of only a few dozen, or maybe a few hundred, people in the world who understands virtual terminals at the lowest level. Htop is clearly doing the Wrong Thing™, using behavior that became obsolete before the Linux kernel even *existed*. There is absolutely *no* excuse for programs written since 1991 to use it.) You're doing *something* wrong, since the kernel's terminal emulator doesn't support underlining. You *must* use ctrl-alt-F1 and reproduce there. Also, in order to have the problem in the first place in htop, you have to have htop's option set, in setup -> display options -> shadow other user's processes On Mon, Jan 23, 2017 at 11:30 PM, Daniel Lange <dl....@usrlocal.de> wrote: > Control: severity -1 minor > Control: tags -1 moreinfo > > TERM=xterm-256color htop # works in xterm from Jessie. No issues. > TERM=linux-16color htop # works, looks ugly (underlines) > > So this all works as intended. Obviously a bad choice of terminal > emulation will lead to ugly rendering. I *assume* the original reporter > also had a weird combination of the TERM variable and terminal > application and that led to only highlighted lines rendering readably. > > It is not possible for htop to render correctly in all cases where > people have broken terminfo, esp. people sshing from Macs etc. >
