From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] History of top
Date: Tue, 29 May 2018 11:48:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1805291147350.75317@frieza.hoshinet.org> (raw)
In-Reply-To: <CAC20D2NQyUKZBp-EPC4bzG6=xkxSZj=vKmvWTthbKg-Yyga-fg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Tue, 29 May 2018, Clem Cole wrote:
> This was really to tell the user, when the system would get to your
> work. BTW, ^T was cool on Tenex, because being interactive, it was just
> your process and helped you know how where your 'active' process stood
> relative to the other things the system was doing (i.e. was it running or
> waiting and how busy was the system as a whole).
I found ^T useful on FreeBSD, where it does more or less the same thing.
-uso.
next prev parent reply other threads:[~2018-05-29 15:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 22:43 Nelson H. F. Beebe
2018-05-29 0:16 ` Clem cole
2018-05-29 1:34 ` Lyndon Nerenberg
2018-05-29 6:53 ` Lars Brinkhoff
2018-05-29 14:18 ` Clem Cole
2018-05-29 15:10 ` Arthur Krewat
2018-05-29 15:48 ` Steve Nickolas [this message]
2018-05-29 16:54 ` Paul Winalski
2018-05-29 17:08 ` Arthur Krewat
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 21:35 Norman Wilson
2018-05-29 21:45 ` Arthur Krewat
2018-05-29 18:55 Noel Chiappa
2018-05-29 19:14 ` Clem Cole
2018-05-29 20:11 ` Dan Cross
2018-05-29 20:57 ` Arthur Krewat
2018-05-30 5:05 ` Lars Brinkhoff
2018-05-24 12:20 Noel Chiappa
2018-05-24 14:09 ` Clem Cole
2018-05-24 14:43 ` Ronald Natalie
2018-05-28 10:31 ` Lars Brinkhoff
2018-05-24 6:14 Lars Brinkhoff
2018-05-24 9:35 ` Dave Horsfall
2018-05-24 10:58 ` jason-tuhs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.02.1805291147350.75317@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).