doc: document 'scale_tics' function for Ctrl-E scaling
[ i also tweaked that 'STARTED' narrative just a bit ] [ since its original wording implied the value could ] [ change, whereas it's fixed when a task is started. ] Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
parent
402bf1903b
commit
5c4c239257
3
NEWS
3
NEWS
@ -32,7 +32,8 @@ procps-ng-NEXT
|
||||
* top: summary area memory lines can print two abreast
|
||||
* top: added two new autogroup fields
|
||||
* top: added long versions of command line options
|
||||
* top: added 'start time' and 'cpu utilization' fields
|
||||
* top: added cpu utilization & 2 time related fields
|
||||
* top: the time related fields can now be user scaled
|
||||
* uptime: print short/pretty format correctly issue #217
|
||||
* vmstat: add -y option to remove first line merge !72
|
||||
|
||||
|
24
top/top.1
24
top/top.1
@ -753,6 +753,8 @@ Thus, the most recently started task will display the smallest time interval.
|
||||
|
||||
The value will be expressed as 'HH,MM' (hours,minutes) but is subject to
|
||||
additional scaling if the interval becomes too great to fit column width.
|
||||
At that point it will be scaled to 'DD+HH' (days+hours) and possibly
|
||||
beyond.
|
||||
|
||||
.TP 4
|
||||
\fBENVIRON \*(Em Environment variables \fR
|
||||
@ -992,10 +994,9 @@ login shell.
|
||||
The length of time since system boot when a process started.
|
||||
Thus, the most recently started task will display the largest time interval.
|
||||
|
||||
The value will be expressed as 'MM:SS' (minutes:sceonds) until the
|
||||
interval becomes too great to fit column width.
|
||||
At that point it will be scaled to 'HH,MM' (hours,minutes) and possibly
|
||||
beyond.
|
||||
The value will be expressed as 'MM:SS' (minutes:seconds).
|
||||
But if the interval is too great to fit column width it will be scaled
|
||||
as 'HH,MM' (hours,minutes) and possibly beyond.
|
||||
|
||||
.TP 4
|
||||
\fBSUID \*(Em Saved User Id \fR
|
||||
@ -1261,7 +1262,7 @@ depending on the context in which they are issued.
|
||||
C, l, t, m, 1, 2, 3, 4, !
|
||||
4c.\fI Task-Area-Commands \fR
|
||||
Appearance: b, J, j, x, y, z
|
||||
Content: c, F, f, O, o, S, U, u, V, v
|
||||
Content: c, F, f, O, o, S, U, u, V, v, ^E
|
||||
Size: #, i, n
|
||||
Sorting: <, >, f, R
|
||||
4d.\fI Color-Mapping \fR
|
||||
@ -1800,6 +1801,19 @@ vertical scrolling.
|
||||
If the target process has not forked any children, this key has no effect.
|
||||
It also has no effect when not in forest view mode.
|
||||
|
||||
.TP 7
|
||||
\ \ \fB^E\fR\ \ :\fIScale-CPU-Time-fields\fR (Ctrl key + `e')
|
||||
The `time' fields are normally displayed with the greatest
|
||||
precision their widths permit.
|
||||
This toggle reduces that precision until it wraps.
|
||||
It also illustrates the scaling those fields \fImight\fR experience
|
||||
automatically, which usually depends on how long the system runs.
|
||||
|
||||
For example, if 'MMM:SS.hh' is shown, each ^E keystroke would change
|
||||
it to: 'MM:SS', 'Hours,MM', 'Days+Hours' and finally 'Weeks+Days'.
|
||||
|
||||
Not all time fields are subject to the full range of such scaling.
|
||||
|
||||
.\" ..................................................
|
||||
.PP
|
||||
.B SIZE\fR of \*(TW
|
||||
|
Loading…
Reference in New Issue
Block a user