Whoops forgot reply-all again: I downloaded the source code and have been looking through it a bit and I think I'm onto something. I noticed that it's not just F5 that causes the problem but any keypress whose handler returns HTOP_SAVE_SETTINGS.
Then, it seems that eventually Header_writeBackToSettings() in Header.c is called. This function has an if statement which decides whether to write a "%s(%d)" or just a "%s" for each meter... This looks suspiciously like something that would cause the problem we're seeing. I don't know enough about the code to know what exactly is wrong, but I think I found where to look! On Thu, Jun 15, 2017 at 1:16 AM, Ben Gladstone <ben@gladstone.digital> wrote: > Ah you're right! I hadn't tried it via the setup menu but it's behaving > the same way for me that it is for you. Definitely has something to do with > F5. Thanks, I'm curious to see what it turns out to be > > On Jun 15, 2017 1:11 AM, "Daniel Lange" <dla...@debian.org> wrote: > >> Am 15.06.2017 um 02:00 schrieb Ben Gladstone: >> > I agree it's really strange and it doesn't make sense to me either why >> > it would be doing that. I thought maybe it had something to do with my >> > F5 key, maybe if there was another keybinding I forgot about. But nope, >> > it has the same behavior when I use the mouse to click on tree mode too. >> > I'll play around with it and see if I can get a clearer picture on the >> > conditions that cause it >> >> Pressing F5 is the critical hint. I changed tree view view the Setup >> menu and then you don't see that behaviour. But changing with F5 I can >> reproduce it as well. Very strange! >> I'll forward upstream. >> >>
