The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] screen editors (FRED)
Date: Wed, 08 Jan 2020 13:43:43 -0800	[thread overview]
Message-ID: <m1ipJ7A-0036tPC@more.local> (raw)
In-Reply-To: <CAC20D2Me2VxTbeX0nLZ74Q9+DSYcTA+oMEsBozS=HdRVWwsLrg@mail.gmail.com>

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

At Tue, 7 Jan 2020 10:03:57 -0500, Clem Cole <clemc@ccc.com> wrote:
Subject: Re: [TUHS] screen editors
>
> FWIW: When I went from PDP-10 land to UNIX, I learned ed for 5th edition
> and somewhat pined for a screen editor.   Soon after upgrading to 6th
> edition at CMU, we found a visual editor called Fred - the Friendly Editor,
> from Cornell IIRC (I think it's on the original USENIX tape but I don't
> remember how we got it).  I had to hack in the Perkin-Elmer Fox terminal
> support, but it was a superset of V6 ed so a pretty trivial learning curve.

Ah, yes, Fred.  A name with so many editors!

I used a full-screen version of an ed-like editor on V7, 32B, and 4BSD
at University of Calgary which was called the "FRiendly EDitor".  This
may be the one you mention.

The FRED I know is not to be confused with the version of QED named FRED
(Friendly Editor) that was written at the University of Waterloo for
Honeywell GECOS by Peter Fraser.  It's also not the "FRED - A Friendly
Editor" by Richard J. Botting [1].  There's also apparently an editor
named FRED for VMS, and another for Amstrad PCW systems (for editing
BASIC, and apparently written in BASIC itself).  And then there's the
one from a company called Digitool which was called "FRED:  Fred
Resembles Emacs Deliberately", which was written in Macintosh Common
Lisp.  There's also an old Windows-based "Friendly Right-to-Left Editor
(FRED)" by NSRI.  I also recently found this [2] reference to a "FRED",
but it seems to be yet another completely different kind of editor using
the same name.

[1] http://www.csci.csusb.edu/dick/papers/rjb84a.FRED.mth

[2] https://www.osti.gov/biblio/5141603-fred-program-development-tool

    Abstract:

    The structured, screen-based editor FRED is introduced.  FRED
    provides incremental parsing and semantic analysis.  The parsing is
    based on an LL(1) top-down algorithm which has been modified to
    provide follow-the-cursor parsing and soft templates.  The languages
    accepted by the editor are LL(1) languages with the addition of the
    Unknown and preferred production non-terminal classes.  The semantic
    analysis is based on the incremental update of attribute grammar
    equations.  We briefly describe the interface between FRED and an
    automated reference librarian system that is under development.

    FRED User's Manual
    Shilling, J.
    Illinois University, Urbana
    Department of Computer Science
    Feb. 1984

    FRED, the frinedly editor, is a screen-based structured editor.
    This manual is intended to serve the needs of a wide range of users
    of the FRED text editor.  Most users will find it sufficient to read
    the introductory material in section 2, supplemented with the full
    command set description in section 3.  Advanced users may wish to
    change the keystroke sequences which invoke editor commands.
    Section 4 describes how to change key bindings and how to define
    command macros.  Some users may need to modify a language
    description or create an entirely new language description for use
    with FRED.  Section 5 describes the format of the language
    descriptions used by the editor, and describes how to construct a
    language grammar.  Section 6 describes known portability problems of
    the FRED editor and should concern only system installation
    personnel.  The editor points out syntax errors in the file being
    edited and does automatic pretty printing.


The version of Fred I used had a full-screen line-oriented mode as well
as what was called "open" mode which presented a much more direct
full-screen editing experience (though it was a bit quirky, but it
reminded me a bit of "Electric Pencil II" which I had used on a Sol-20).
Open mode of course generated an interrupt for every key press and so on
a PDP-11/60 with 16 terminals it could cause quite a system load, and
most of us avoided using open mode on the PDPs.  Even the VAX 11/780
running 32V was sometimes slowed by it, but it had at least 24 terminals
as I recall (at the time it was still running 32V), so a room full of
students feverously typing away was quite a lot of input.

I've been unable to find any other reference or mention of this version
of Fred; and to the best of my searches it's not on any Usenix tape I
can find a copy of.

If anyone has any further info about the FRED Clem and/or I seem to
remember, please do post it!

I soon forgot most that I knew about Fred though once Gosling Emacs was
installed on the VAX (after it had been upgraded to 4BSD).  I already
had a strong preference to Emacs having used it extensively on the
Multics system at UofC.

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-01-08 21:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07  2:31 [TUHS] screen editors Doug McIlroy
2020-01-07  2:37 ` Brantley Coile
2020-01-07  2:38 ` Larry McVoy
2020-01-07 16:30   ` arnold
2020-01-07 16:38     ` Richard Salz
2020-01-07 18:32     ` Dan Cross
2020-01-07 19:14     ` Thomas Paulsen
2020-01-09  5:01       ` Grant Taylor via TUHS
2020-01-10  8:16         ` ricercar
2020-01-08  0:10     ` Jon Steinhart
2020-01-17 22:06       ` Dave Horsfall
2020-01-08 18:30     ` Mary Ann Horton
2020-01-08 21:41       ` Thomas Paulsen
2020-01-09  8:30       ` arnold
2020-01-07  6:19 ` Dave Horsfall
2020-01-07  8:24   ` Thomas Paulsen
2020-01-07 20:44     ` Dave Horsfall
2020-01-08 15:29   ` Steve Mynott
2020-01-08 23:31     ` Dave Horsfall
2020-01-07  9:43 ` ullbeking
2020-01-07 14:53   ` Dan Cross
2020-01-07 19:35   ` Rodrigo G. López
2020-01-08  5:13     ` Mark van Atten
2020-01-07 15:03 ` Clem Cole
2020-01-08 21:43   ` Greg A. Woods [this message]
2020-01-09  0:04     ` [TUHS] screen editors (FRED) Dave Horsfall
2020-01-07 15:50 ` [TUHS] screen editors Thomas Paulsen
2020-01-07 20:45   ` Chet Ramey
2020-01-07 21:20     ` Derek Fawcus

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=m1ipJ7A-0036tPC@more.local \
    --to=woods@robohack.ca \
    --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).