From: Adam Thornton <athornton@gmail.com>
To: 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 17:59:05 -0700 [thread overview]
Message-ID: <CAP2nic1R4yx5EkZ+zAxaZKo4m47kvJgs5bC5L0gULN0oaSTv5A@mail.gmail.com> (raw)
In-Reply-To: <f1548416-6d17-41c1-af89-5d9768943d66@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
I was hoping for a better easter egg. I dunno about y'all but when I see
">>>" .... my mind goes a certain place. Alas, no.
adam@m1-wired:~/git/phalanx/services/nublado$ dc
>>> boot dqa0
Parse error: bad character 't'
<stdin>:1
On Mon, Jan 23, 2023 at 2:09 PM Joseph Holsten <joseph@josephholsten.com>
wrote:
> On Mon, Jan 23, 2023, at 06:15, Dan Cross wrote:
> > On Sun, Jan 22, 2023 at 10:41 PM George Michaelson <ggm@algebras.org>
> wrote:
> >> I should also also add, Mac has >>> as Rob noted. FreeBSD doesn't
> >
> > Hmm, interesting. I wonder what version of macOS you both are running?
> > My old trashcan Mac (soon to be replaced!) is running the
> > next-to-most-recent version and doesn't have the `>>> ` prompt. My
> > laptop, running the latest (Ventura?) does.
> >
> > I don't think I blame Apple for this, but rather something upstream of
> them.
>
> Per https://opensource.apple.com/releases/, they switched from
> macOS Monterey 12 with GNU bc 1.06
> https://github.com/apple-oss-distributions/bc/tree/bc-21/bc
> to macOS 13 with GH bc 4.0.2
> https://github.com/apple-oss-distributions/bc/tree/bc-26/bc
>
> I suspect this is similar to the replacement of bash with zsh for GPL
> avoidance.
>
> Interesting timeline though, https://git.yzena.com/gavin/bc/src/tag/4.0.2
> was released in 2021-05-01, https://git.yzena.com/gavin/bc/src/tag/5.0.0
> in 2021-08-08.
>
[-- Attachment #2: Type: text/html, Size: 2427 bytes --]
next prev parent reply other threads:[~2023-01-24 1:00 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 [this message]
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
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=CAP2nic1R4yx5EkZ+zAxaZKo4m47kvJgs5bC5L0gULN0oaSTv5A@mail.gmail.com \
--to=athornton@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).