bin/54328: top(1) handles first command weirdly if entered too fast

[Thomas Klausner <wiz%NetBSD.org@localhost>]

>Number:         54328
>Category:       bin
>Synopsis:       top(1) handles first command weirdly if entered too fast
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 26 20:30:00 +0000 2019
>Originator:     Thomas Klausner
>Release:        NetBSD 8.99.42
>Organization:
Curiosity is the very basis of education and if you tell me that
curiosity killed the cat, I say only that the cat died nobly.
- Arnold Edinborough
>Environment:
	
	
Architecture: x86_64
Machine: amd64
>Description:
top handles the first key press weirdly if it's given too quickly after start.

On startup, some of the data is not shown yet, in particular the percentages, i.e.

CPU states:     % user,     % nice,     % system,     % interrupt,     % idle

On my machine it takes 1-2s until it gets replaced with actual values:

CPU states:  0.0% user,  0.0% nice,  0.5% system,  0.0% interrupt, 99.4% idle

If you press a key during that time, you can enter the necessary arguments,
but it doesn't have an immediate effect, or it's ignored.

Examples:

When you wait and press 'u' to limit to a user, after entering the user name
the display is immediately switched to show only that user; if you do that
in the first second, you have to wait for the automatic update after 5s for
it to take effect.

Similar effect for 'U'.

If you press 's' to set a new refresh interval, it's completely ignored
and stays at 5s.
>How-To-Repeat:
Start top and enter a command immediately.
>Fix:
If you're bored, yes, please.

>Unformatted: