The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ken Thompson <kenbob@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] manual humour (was tunefs -m 5%)
Date: Wed, 10 Mar 2021 12:17:35 -0800	[thread overview]
Message-ID: <CAMP=X_mrCNQXN1BrCoaUHTrDhWjCZMw0-ig9iFnry4Te96i_DQ@mail.gmail.com> (raw)
In-Reply-To: <CALMnNGg-ByEm27qiS+D9S_HwnSf2Dsb7XG8RkgnZEVb5C9Ri=Q@mail.gmail.com>

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

back to original title - manual humour.
my favorite was in the "form" command.
-- credit to mcilroy.

"If one of the special characters [{]}\ is preceded
by a \, it loses its special character."


On Wed, Mar 10, 2021 at 11:50 AM Andy Kosela <akosela@andykosela.com> wrote:

> On 3/10/21, Andreas Kusalananda Kähäri <andreas.kahari@abc.se> wrote:
> > On Tue, Mar 09, 2021 at 06:51:56PM -0500, Steve Nickolas wrote:
> >> On Wed, 10 Mar 2021, Rob Pike wrote:
> >>
> >> > I'm curious when people (other than me) erred and stopped saying that
> >> > ed
> >> > was the standard editor.
> >> >
> >> > -rob
> >> >
> >>
> >> I actually use that expression in somewhat unorthodox ways. ;)
> >>
> >> Like "CDE is the standard desktop environment like ed is the standard
> >> text
> >> editor." (I still consider both to be true even though about no one uses
> >> either anymore.)
> >>
> >> -uso.
> >
> > Hi, I'm "about no one".  I use ed(1) every once in a while, both the
> > way it was supposed to be used, i.e. interactively, and occasionally
> > scripted on smaller documents.
> >
> > I'm soon 50.  Having grown up with computers, and having spent most of
> > my money as a student buying the next bigger and/or faster PC, I find
> > that I nowadays enjoy smaller, slower systems and simpler editors more
> > and more.  Getting distracted by syntax highligting, confused by too
> > complicated configurations... There is a certain beauty in the editing
> > language of ed(1).  It's minimalistic and restrictive, and therefore
> > forces you to think, to remember, and to be creative.
>
> This comment resonates with me so much.  I am enjoying these days
> mostly retro systems too -- computers I grew up with.  There is a
> certain beauty in the term "less is more".  And nothing is more
> satisfying than sitting in front of a CRT terminal (either some real
> terminal or PC) and working in a full screen text mode.  No GUIs, no
> distractions -- just pure conversation with a machine using only text.
> That's UNIX for me.
>
> These days there have been a huge resurgence of various retro
> communities around the world.  There are still tons of new programs
> and games being published for 8-bit micro's or Amiga's.  Still it
> appears the Unix community in general is not part of that movement.  I
> think TUHS is an exception and a haven for people who just prefer the
> old ways.  I find Unix these days too bloated and moved away from its
> main core values: simplicity and minimalism.  The hardware was much
> simpler too back in the days.
>
> Long live the ed(1) and vi(1).
>
> --Andy
>

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

  reply	other threads:[~2021-03-10 20:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 16:21 Norman Wilson
2021-03-09 20:11 ` Henry Bent
2021-03-09 20:22   ` Steffen Nurpmeso
2021-03-09 20:36     ` Henry Bent
2021-03-09 22:30       ` Rob Pike
2021-03-09 22:46         ` Larry McVoy
2021-03-09 23:51         ` Steve Nickolas
2021-03-10  0:01           ` Rob Pike
2021-03-10  0:13             ` Anthony Martin
2021-03-10 18:37           ` Andreas Kusalananda Kähäri
2021-03-10 19:49             ` Andy Kosela
2021-03-10 20:17               ` Ken Thompson [this message]
2021-03-10 20:30                 ` Rob Pike
2021-03-11  3:54                   ` George Michaelson
2021-03-11  4:57                     ` Will Senn
2021-03-10  2:34         ` Nemo Nusquam
2021-03-12  2:48         ` John Cowan

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='CAMP=X_mrCNQXN1BrCoaUHTrDhWjCZMw0-ig9iFnry4Te96i_DQ@mail.gmail.com' \
    --to=kenbob@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).