cgzones

@Dale-M What was the specific reason for this? Does opening `/dev/tty` failed or did the content written to it not showed up? This change (just yet landed in Debian unstable)...

It seems to work. May I ask why less opens a new file descriptor in the first place? What's wrong with the inherited `STDIN_FILENO` (at least on Linux)?

To minimize the size of the header for systems with many CPUs https://github.com/htop-dev/htop/commit/8fb51627b2e116d7957f57f27aff31ea726d7d86 tweaked the default configuration to select a CPU meter with appropriate columns. One can switch to another...

Maybe due to https://github.com/htop-dev/htop/commit/d9f2eacbc5b3fccf63b24944ce9a30d762baea3c and https://github.com/htop-dev/htop/commit/2d7069feb43bf20a7ad018aa3a11025e1f34c2ec. Does the system uses ZFS?

The htop color scheme `Broken Gray` was designed for these terminals. Its also not just about `$TERM` as on some systems `TERM=screen ./htop` works fine. #251 is probably related.

Only the the first (whatever the kernel decides to be first) non-loopback link-local IP address is displayed. Maybe in the future Meters can have runtime options, which can be set...

The original idea was to shadow paths used by distribution packages. It was not about "trusted" (e.g. /root/bin could be considered trusted) or common (like /usr/local/bin) ones.

You have `show_thread_names` and `show_merged_command` set to `0`. When setting them `COMM` is included.

Can reproduce on Debian sid with `libnss-systemd` installed and a service with `DynamicUser=yes` running: ```gdb Starting program: /home/christian/Coding/workspaces/htop/htop > run.txt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1"....

@yong718100 could you give #1066 a try?