Hi Tim,
There were a series of changes to top key handling in release 4.0.1
prompted by the new 'bottom window' feature (^G, ^N, etc).
Unfortunately, they adversely impacted screen refresh.
That was corrected in release 4.0.4, essentially restoring the former
3.3.17 behavior.
Regards,
Jim
Package: procps
Version: 2:4.0.2-3
Severity: normal
The version of top in bookworm seems to have changed the processing of
the keybinding for :Refresh-Display, and you can see it
immediately drawing the screen *twice* while registering the current
`top` process as something taking 100% of the CPU
2 matches
Mail list logo
