The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: James Johnston <audioskeptic@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: "9 skills our grandkids won't have" - Is this a TUHS topic?
Date: Thu, 30 Jun 2022 14:41:26 -0700	[thread overview]
Message-ID: <CAO2qRdNnFi3HNP-cDZe_8GU1-D8AkMK0PoaKWEurLQUOm8iaOA@mail.gmail.com> (raw)
In-Reply-To: <CALQ0xCA4fH6Jp9N+_fg4h3wuxqNmGuSynnVFsSbXtAyZKS-ueQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

Loading your 18" gigantic 5 MB disc in the tray, and giving it 5 minutes to
temperature equalize.

On Thu, Jun 30, 2022 at 2:26 PM Marc Donner <marc.donner@gmail.com> wrote:

> And, of course, even worse editing with cat!
> =====
> nygeek.net
> mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>
>
>
> On Thu, Jun 30, 2022 at 5:22 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>> When your tty settings are messed up, ed(1) has saved my butt a number
>> of times.  Also really pleasant to use on slow modems where just the
>> screen refresh takes a long time.
>>
>> ed foo.c
>> /^busted_function
>> .,.+20p
>>
>> is dramatically faster than vi(1) at 300 baud.
>>
>> On Thu, Jun 30, 2022 at 09:49:19PM +0100, Chris Pinnock via TUHS wrote:
>> > Editing /etc/inittab with ed(1).
>> >
>> > > On 30 Jun 2022, at 21:43, Robert Stanford via TUHS <tuhs@tuhs.org>
>> wrote:
>> > >
>> > > editing /etc/inittab
>> > >
>>
>> --
>> ---
>> Larry McVoy            Retired to fishing
>> http://www.mcvoy.com/lm/boat
>>
>

-- 
James D. (jj) Johnston

Chief Scientist, Immersion Networks

[-- Attachment #2: Type: text/html, Size: 2244 bytes --]

  reply	other threads:[~2022-06-30 21:43 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 13:14 [TUHS] " steve jenkin
2022-06-30 13:39 ` [TUHS] " Marc Donner
2022-06-30 13:54   ` Tom Teixeira
2022-06-30 14:08   ` Marshall Conover
2022-06-30 14:15     ` Larry McVoy
2022-06-30 14:32     ` Will Senn
2022-06-30 14:42     ` Pierre DAVID
2022-06-30 15:44       ` Larry McVoy
2022-06-30 15:23   ` Clem Cole
2022-06-30 15:35     ` Clem Cole
2022-06-30 14:23 ` Michael Kjörling
2022-06-30 15:12 ` Al Kossow
2022-06-30 15:55 ` Adam Thornton
2022-06-30 16:37 ` Paul Winalski
2022-07-01 13:05   ` Ori Idan
     [not found]     ` <Yr7zs59NtbXcRCu4@mbsks.franken.de>
2022-07-01 13:17       ` Matthias Bruestle
2022-07-01 13:36         ` Angus Robinson
2022-07-01 13:58           ` Marc Donner
2022-07-01 14:05             ` Henry Bent
2022-07-01 14:37               ` Marc Donner
2022-07-01 14:41           ` Blake McBride
2022-09-16 17:04         ` Michael Parson
2022-07-02 23:01     ` Mark Sutton
2022-07-03  0:08       ` John Cowan
2022-06-30 19:24 ` Michael Huff
2022-06-30 19:56   ` Jon Steinhart
2022-06-30 20:43   ` Robert Stanford via TUHS
2022-06-30 20:49     ` Chris Pinnock via TUHS
2022-06-30 21:11       ` ron minnich
2022-06-30 21:21       ` Larry McVoy
2022-06-30 21:24         ` Marc Donner
2022-06-30 21:41           ` James Johnston [this message]
2022-06-30 21:54             ` Larry McVoy
2022-06-30 22:05               ` Dr Iain Maoileoin
2022-06-30 22:18                 ` Rik Schneider
2022-06-30 22:51                   ` Marc Donner
2022-07-01 10:48                   ` Tom Ivar Helbekkmo via TUHS
2022-06-30 21:24         ` Chris Pinnock via TUHS
2022-07-01  0:41 ` Tomasz Rola
2022-07-01  0:46   ` Larry McVoy
2022-07-01  1:13     ` Larry Stewart
2022-07-01 18:12   ` Harald Arnesen
2022-07-01 13:31 Nelson H. F. Beebe
2022-07-01 14:02 ` Steve Nickolas
2022-07-01 15:01   ` Clem Cole
2022-07-01 19:22     ` Phil Budne
2022-07-01 19:53       ` Clem Cole
2022-07-02 19:36     ` Leah Neukirchen
2022-07-02 19:50       ` Clem Cole
2022-07-03  0:22       ` John P. Linderman
2022-07-01 15:50   ` Lars Brinkhoff
2022-07-01 16:20     ` Warner Losh
2022-07-01 18:18       ` Clem Cole
2022-07-01 18:09     ` Clem Cole
2022-07-01 18:45     ` Steve Nickolas

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=CAO2qRdNnFi3HNP-cDZe_8GU1-D8AkMK0PoaKWEurLQUOm8iaOA@mail.gmail.com \
    --to=audioskeptic@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).