The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] Make love
Date: Sat, 01 Aug 2015 18:35:22 -0700	[thread overview]
Message-ID: <55BD73DA.3010107@mhorton.net> (raw)
In-Reply-To: <a0849a67fc17435f62770a93a402c99e.squirrel@webmail.yaccman.com>

Oh, I remember "Very funny!"  It was pr, V6, I think.

I wanted to format for a 132 wide printer and I mistakenly typed "pr 
-132 file" instead of "pr -w132 file".  It thought I wanted it formatted 
in 132 columns of text.

I about tore my hair out trying to figure out what "Very funny!" meant.

On 07/31/2015 07:42 PM, scj at yaccman.com wrote:
> Early Unix had a lot of cryptic messages -- the infamous "eh?", and "very
> funny!" were two that I got several times.  The make love message in the
> earliest make I remember was "Don't know how to make love."
>
> When working on PCC, I had the unenviable job of producing a C compiler
> that would accept all of  *077532 = 13, 077532->ack = 13, and device->ack
> = 13.  As we were trying to get the kernel and applications to declare
> addresses more "honestly", we adopted a rule that if you actually used a
> structure reference that was type safe, we would require it everywhere in
> the file.  Since structure members used to be in a single namespace, this
> led to some horribly complicated code.  In an effort to get it to work, I
> festooned it with consistency checks nearly every other line, getting more
> and more punchy as I tried to come up with short, unique messages.
>
> I'll never forget the look on Ken's face when he came to me and asked
> "what is a 'gummy structure'?"
>
> Nowadays, while I'm happy to have some fun with them, I think throwing
> humor at people who have just screwed up is playing to a tough audience.
> Today, I might have suggested that 'make love' produce something more like
> "Don't know how to make love.  Can you introduce me to a hot makefile?"
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs




  reply	other threads:[~2015-08-02  1:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 17:23 Norman Wilson
2015-07-31 21:05 ` Warner Losh
2015-07-31 23:48   ` John Cowan
2015-08-01  3:48     ` Larry McVoy
2015-08-01  2:42   ` scj
2015-08-02  1:35     ` Mary Ann Horton [this message]
2015-08-02  9:45     ` arnold
2015-08-10 17:51       ` scj
2015-08-01  3:20   ` Dave Horsfall
2015-08-01  3:36     ` Steve Nickolas
2015-08-01 11:19       ` Milo Velimirovic
2015-08-01 11:28         ` Milo Velimirovic
2015-08-01  3:50     ` Larry McVoy
2015-08-01  4:53       ` Steve Nickolas
2015-08-01 17:02       ` Clem cole
2015-08-01 17:04       ` Clem cole
2015-08-01  7:21     ` Warner Losh
2015-08-01 11:16       ` Ronald Natalie
  -- strict thread matches above, loose matches on Subject: below --
2015-08-01 11:03 Norman Wilson
2015-07-31  0:16 Nemo
2015-07-30 21:11 Norman Wilson
2015-07-30 20:00 Dave Horsfall
2015-07-30 20:03 ` John Cowan
2015-07-31 16:32   ` ron
2015-07-31 16:39     ` John Cowan
2015-07-30 20:37 ` Ori Idan
2015-07-30 20:45   ` Chet Ramey
2015-07-30 20:51   ` Jaap Akkerhuis
2015-07-31 16:09     ` random832
2015-07-31 16:40       ` Warner Losh
2015-07-31 17:00         ` Ed Skinner

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=55BD73DA.3010107@mhorton.net \
    --to=mah@mhorton.net \
    /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).