The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: python
Date: Fri, 4 Aug 2023 13:15:51 -0700	[thread overview]
Message-ID: <20230804201551.GL24315@mcvoy.com> (raw)
In-Reply-To: <20230804201102.753C218C077@mercury.lcs.mit.edu>

Perhaps it is a stretch, but I'd say that printf() is a good example of
the type of thinking done by the original Unix folks.  Seeing how other
people didn't learn that lesson kind of underscores the good engineering
done at Bell Labs.

On Fri, Aug 04, 2023 at 04:11:02PM -0400, Noel Chiappa wrote:
> How is discussing Python's output options related to the history of Unix?
> 
> 	Noel

-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2023-08-04 20:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 20:11 Noel Chiappa
2023-08-04 20:15 ` Larry McVoy [this message]
2023-08-04 20:45   ` Adam Thornton
  -- strict thread matches above, loose matches on Subject: below --
2023-08-06 19:46 Norman Wilson
2023-08-07  6:48 ` Ed Bradford
2023-08-04 21:17 Douglas McIlroy
2023-08-04 21:30 ` Dan Cross
2023-08-04 22:36 ` Rob Pike
2023-07-30 23:59 [TUHS] Re: Cool talk on Unix and Sendmail history, by Eric Allman Erik E. Fair
2023-08-01 10:58 ` Erik E. Fair
2023-08-02  0:37   ` Dave Horsfall
2023-08-02 14:52     ` Ron Natalie
2023-08-02 21:14       ` Grant Taylor via TUHS
2023-08-02 22:20         ` segaloco via TUHS
2023-08-02 23:49           ` Rich Salz
2023-08-03  0:51             ` [TUHS] Re: python Larry McVoy
2023-08-03  1:20               ` George Michaelson
2023-08-03  2:53                 ` Bakul Shah
2023-08-03  2:55                 ` segaloco via TUHS
2023-08-03  3:24                 ` George Michaelson
2023-08-03  3:32                   ` Warner Losh
2023-08-03  3:55                   ` Bakul Shah
2023-08-03  8:32                     ` Rob Pike
2023-08-03 14:19                       ` Bakul Shah
2023-08-03 14:56                         ` Dan Halbert
2023-08-03 15:20                           ` will.senn
2023-08-03 22:05                             ` Dan Cross
2023-08-04  0:24                               ` John Cowan
2023-08-04 15:17                                 ` Dan Cross
2023-08-05  4:44                               ` Bakul Shah
2023-08-03 15:41                         ` John Cowan
2023-08-03  2:07               ` Clem Cole
2023-08-03  2:21                 ` Pete Wright via TUHS
2023-08-03  2:56                   ` Warner Losh
2023-08-03 12:36                 ` Mike Markowski
2023-08-03 13:29                   ` Rob Pike
2023-08-03 15:24                     ` emanuel stiebler
2023-08-03 15:39                       ` Steffen Nurpmeso
2023-08-04  1:01                     ` Larry McVoy
2023-08-04  1:28                       ` segaloco via TUHS
2023-08-04  1:58                         ` Adam Thornton
2023-08-04 15:04                           ` Dan Cross
2023-08-04 15:10                             ` Larry McVoy
2023-08-04 19:20                 ` Ed Bradford
2023-08-04 19:47                   ` Larry McVoy
2023-08-05  5:40                     ` Ed Bradford

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=20230804201551.GL24315@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).