The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Qed vs ed
Date: Sat, 30 Jan 2021 21:58:29 -0600	[thread overview]
Message-ID: <51d043be-4905-f4b2-c46e-34427c43a61d@gmail.com> (raw)
In-Reply-To: <f2330b8f-6273-e2dc-526b-901298fff5ee@gmail.com>

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

On 1/30/21 9:48 PM, Will Senn wrote:
> On 1/30/21 9:16 PM, Will Senn wrote:
>> Hi all,
>>
>> So. On a lighter note. I was tooling around the web and came across a discussion of QED, the editor. It’s been resurrected in no small part based on discussions on this list (and members like Rob Pike). Anyhow, there’s a version that compiles in modern systems and that handles wide characters. My question for the group is this how different is QED from ed? I’ve read Dennis’ paper on the history of QED and it’s fascinating, but all I really got out of the discussion related to ed, was that QED was a precursor. I’m curious about functional parity or lack thereof, more than technical differences. In full disclosure, and at the risk of drawing fire from lovers of other editors, I have to confess a love of the original ed (and it’s decendent ed’s and vi).
>>
>> Cheers,
>>
>> Will
>>
>>
>>
>> Sent from my iPhone
> Here's the link to the article that kicked off this line of inquiry:
>
> https://leahneukirchen.org/blog/archive/2021/01/remembering-the-work-of-david-m-tilbrook-and-the-qed-editor.html
>
> Does anyone know of any effort to show the family tree of editors, 
> similar to what we have for unix and linux?
>
> Will
Ah, heck - Dennis says QED influenced ed, but the first line of the 
description in QED (1) (Mar/82) is:

Qed is a multiple-file programmable text editor based on ed.

Which is it?

Will

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

  reply	other threads:[~2021-01-31  3:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  3:16 Will Senn
2021-01-31  3:48 ` Will Senn
2021-01-31  3:58   ` Will Senn [this message]
2021-01-31  4:07   ` Al Kossow
2021-01-31  7:00     ` Lars Brinkhoff
2021-01-31  8:29       ` Rob Pike
2021-01-31  9:28         ` Jaap Akkerhuis
2021-01-31 10:04     ` arnold

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=51d043be-4905-f4b2-c46e-34427c43a61d@gmail.com \
    --to=will.senn@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).