Whoops forgot to hit reply-all, resending: Alright I just tried that and I'm still seeing the strange behavior. I deleted htoprc and opened htop, then quit. I've attached the htoprc file it created as "htoprc.start"
Then, I reopened htop and added a "CPU 1" meter, then quit htop. I've attached the htoprc at this stage as "htoprc.cpu1". I reopened htop to make sure it was still there, and it was fine. Then, I toggled tree view on and quit htop. Upon reopening htop, the "CPU 1" meter had changed to a "CPU AVG" meter. I've attached the htoprc from this stage as "htoprc.aftertreeview". For some reason it changed the meter entry "CPU(1)" into just "CPU" upon entering tree view. I'm not sure if tree view is the only thing that causes this to happen, but it's the only time I've noticed it so far. Let me know if there's any other information about my system configuration that would be useful. On Tue, Jun 13, 2017 at 12:46 PM, Daniel Lange <dla...@debian.org> wrote: > Control: severity -1 minor > > Hi Ben, > > thanks a lot for submitting the bug report. > I can't verify the issue here. I can create and persist a "CPU 2" meter > all I want and it shows up independent of tree view or not. > > Could you look at .config/htop/htoprc and possibly move that out of the > way so htop creates a fresh one. Does that "fix" the issue? > > Kind regards, > Daniel > > >
htoprc.aftertreeview
Description: Binary data
htoprc.cpu1
Description: Binary data
htoprc.start
Description: Binary data
