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
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
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
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