From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] BDS C (was: Screen editors)
Date: Sat, 8 Feb 2020 11:32:28 +1100 [thread overview]
Message-ID: <20200208003228.GB75158@eureka.lemis.com> (raw)
In-Reply-To: <CAFH29toQBtYGdyis9Cbs4fzxwxrPjoVVaK40jJ9_L+0jQP7rLw@mail.gmail.com>
Moving to COFF to avoid the wrath of wkt.
On Friday, 7 February 2020 at 18:54:33 -0500, Richard Salz wrote:
> BDS C stood for Brain-Damaged Software, it was the work of one guy (Leor
> Zolman). I think it was used to build the Mark of the Unicorn stuff
> (MINCE, Mince is not complete emacs, and Scribble, a scribe clone).
Correct. That's how I came in contact with it (and Emacs, for that
matter).
Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200208/b31fe31c/attachment.sig>
next parent reply other threads:[~2020-02-08 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200120155946.169b39e0.ref@sagittariusa.cnb.csic.es>
[not found] ` <20200120155946.169b39e0@sagittariusa.cnb.csic.es>
[not found] ` <dfb57629-a249-fe46-5d69-48708d91be43@telegraphics.com.au>
[not found] ` <alpine.BSF.2.21.9999.2001300918470.15513@aneurin.horsfall.org>
[not found] ` <20200129223322.GK6410@mcvoy.com>
[not found] ` <alpine.BSF.2.21.9999.2002081001130.33501@aneurin.horsfall.org>
[not found] ` <CAFH29toQBtYGdyis9Cbs4fzxwxrPjoVVaK40jJ9_L+0jQP7rLw@mail.gmail.com>
2020-02-08 0:32 ` grog [this message]
2020-02-08 1:10 ` lm
2020-02-08 2:37 ` clemc
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=20200208003228.GB75158@eureka.lemis.com \
--to=coff@minnie.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).