The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: interesting case of not getting the point: dc on a mac
Date: Mon, 23 Jan 2023 12:32:10 +1100	[thread overview]
Message-ID: <CAKzdPgzD5bhfLiSix=G6QuxCTgqaVMEU3_Y9wZMfaftzdxOaBw@mail.gmail.com> (raw)
In-Reply-To: <F810CF74-9EDC-40CB-872A-23D28531CBB1@iitbombay.org>

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

Pretty much everything in the dc man page on my mac raises my hackles. Not
limited to changing behavior when you're on a TTY. (Also: NO ONE HAS BEEN
ON A TTY FOR DECADES!)

I am such an old grump.

-rob


On Mon, Jan 23, 2023 at 11:41 AM Bakul Shah <bakul@iitbombay.org> wrote:

> Probably because MacOS moved things around or is intent on breaking things?
> I didn't investigate. It compiles fine on FreeBSD.
>
> On Jan 22, 2023, at 4:20 PM, ron minnich <rminnich@gmail.com> wrote:
>
> How do you write a dc that doesn't compile?
>
> The mind reels.
>
> On Sun, Jan 22, 2023, 7:16 PM Bakul Shah <bakul@iitbombay.org> wrote:
>
>> dc -V on MacOS shows 4.0.2. Repo link in the output of dc -V.
>> The current version is 6.2.2 but it doesn't compile on Ventura.
>>
>> > On Jan 22, 2023, at 3:39 PM, ron minnich <rminnich@gmail.com> wrote:
>> >
>> > dc
>> > >>>
>> >
>> > it prompts with '>>> '
>> >
>> > wonder where that came from? First time I've seen it.
>> >
>> > Seems to have a certain lack of understanding attached to it.
>>
>>
>

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

      reply	other threads:[~2023-01-23  1:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 23:39 [TUHS] " ron minnich
2023-01-22 23:41 ` [TUHS] " ron minnich
2023-01-22 23:50   ` Warner Losh
2023-01-22 23:49 ` Steve Nickolas
2023-01-22 23:57   ` Joseph Holsten
2023-01-23  0:07     ` Steve Nickolas
2023-01-23  3:07   ` Dave Horsfall
2023-01-23  3:11     ` Larry McVoy
2023-01-23 13:43       ` Dan Cross
2023-01-23 13:59         ` ron minnich
2023-01-23  3:32     ` Steve Nickolas
2023-01-23  3:38       ` George Michaelson
2023-01-23  3:39         ` George Michaelson
2023-01-23  3:40           ` George Michaelson
2023-01-23 14:15             ` Dan Cross
2023-01-23 21:08               ` Joseph Holsten
2023-01-24  0:59                 ` Adam Thornton
2023-01-23  0:15 ` Bakul Shah
2023-01-23  0:20   ` ron minnich
2023-01-23  0:23     ` George Michaelson
2023-01-23  0:26     ` Joseph Holsten
2023-01-23  0:39     ` Bakul Shah
2023-01-23  1:32       ` Rob Pike [this message]

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='CAKzdPgzD5bhfLiSix=G6QuxCTgqaVMEU3_Y9wZMfaftzdxOaBw@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=bakul@iitbombay.org \
    --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).