unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: editor and word processor history (was: Re: RTF for emacs)
Date: Thu, 29 May 2014 21:10:42 -0700 (PDT)	[thread overview]
Message-ID: <d4d71a02-c013-4544-a1dc-4190d496c38d@googlegroups.com> (raw)
In-Reply-To: <mailman.2501.1401420691.1147.help-gnu-emacs@gnu.org>

On Friday, May 30, 2014 9:01:18 AM UTC+5:30, Bob Proulx wrote:
> Allan Streib wrote:
> > Emanuel Berg writes:
> > > For the Unix world, I have read there was once an
> > > editor called ed that didn't showed the file being
> > > manipulated at all - the "state" of the file, as it was
> > > called (unbelievable).

> Once was and still is too.  The GNU ed is available.

>   http://www.gnu.org/software/ed/

> > Teletypes and other brands of paper-based "terminals" were commonplace
> > then. You didn't need (nor was it practical) for the editor to display
> > the contents of the file, when it was already printed on the paper in
> > front of you. So you used sed-like search/replace commands.

> When I was at university I wrote thousands of lines of code using qed
> (a precurser to ed on the old Honeywell GCOS system) and paper
> terminals over acoustic coupled modems.  If nothing else it will teach
> you how to use regular expressions at a very deep level!  Editors like
> ed are actually very efficient if you know how to use them.

> > Even the first CRTs were dumb (aka "glass teletypes") and didn't have
> > addressable cursors. You cloud clear and redraw the screen maybe, which
> > was painful at 110 or 300 baud.

> Agreed.  Very painful.  From first hand experience.

> Here is a funny modern day ed story.
:
:
> I still prefer emacs however.

Yeah I had a friend who staunchly believed that using ed
would clarify the thoughts and purify the soul.

I sometimes get the feel that we emacs users look like analogous cartoons to
the current generation.


  parent reply	other threads:[~2014-05-30  4:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1964.1400890902.1147.help-gnu-emacs@gnu.org>
2014-05-24  0:53 ` RTF for emacs Emanuel Berg
2014-05-25 19:24   ` Robert Thorpe
2014-05-25 20:38     ` James Freer
2014-05-26  1:15     ` Stefan Monnier
2014-05-26  1:49       ` Robert Thorpe
2014-05-26  3:41         ` Stefan Monnier
     [not found]         ` <mailman.2103.1401075744.1147.help-gnu-emacs@gnu.org>
2014-05-26 12:39           ` Rusi
2014-05-26 14:15             ` Rusi
2014-05-26 23:29           ` Emanuel Berg
     [not found]       ` <mailman.2101.1401068969.1147.help-gnu-emacs@gnu.org>
2014-05-26  2:41         ` Rusi
2014-05-26 23:28         ` Emanuel Berg
     [not found]     ` <mailman.2081.1401050318.1147.help-gnu-emacs@gnu.org>
2014-05-29  0:55       ` Emanuel Berg
2014-05-29  1:38         ` editor and word processor history (was: Re: RTF for emacs) Emanuel Berg
2014-05-29  1:41           ` Emanuel Berg
2014-05-29  7:23           ` editor and word processor history Glyn Millington
2014-05-29  9:39           ` editor and word processor history (was: Re: RTF for emacs) James Freer
2014-05-29 13:14           ` Allan Streib
2014-05-29 21:40             ` Robert Thorpe
2014-05-30  3:31             ` Bob Proulx
     [not found]             ` <mailman.2501.1401420691.1147.help-gnu-emacs@gnu.org>
2014-05-30  4:10               ` Rusi [this message]
2014-05-31 23:03                 ` Emanuel Berg
     [not found]           ` <mailman.2380.1401356412.1147.help-gnu-emacs@gnu.org>
2014-05-29 12:32             ` editor and word processor history Haines Brown
2014-05-29 22:58             ` editor and word processor history (was: Re: RTF for emacs) Emanuel Berg
2014-05-30  5:52               ` James Freer
     [not found]               ` <mailman.2505.1401429187.1147.help-gnu-emacs@gnu.org>
2014-05-30 10:37                 ` Emanuel Berg
2014-05-30 19:12                   ` James Freer
     [not found]                   ` <mailman.2563.1401477129.1147.help-gnu-emacs@gnu.org>
2014-05-31 12:44                     ` From: Sharon Kimble, Subject: Re: editor and word processor history Emanuel Berg
2014-05-31 17:23                       ` Barry Margolin
2014-05-31 19:26                         ` Emanuel Berg
2014-05-31 23:17                           ` Sharon Kimble
     [not found]                           ` <mailman.2663.1401578257.1147.help-gnu-emacs@gnu.org>
2014-05-31 23:54                             ` Emanuel Berg
     [not found]           ` <mailman.2390.1401369425.1147.help-gnu-emacs@gnu.org>
2014-05-29 23:38             ` editor and word processor history (was: Re: RTF for emacs) Emanuel Berg
     [not found]           ` <mailman.2376.1401348837.1147.help-gnu-emacs@gnu.org>
2014-05-29 23:51             ` editor and word processor history Emanuel Berg
2014-05-29  5:17         ` RTF for emacs Rusi
2014-05-29 22:49           ` Emanuel Berg
2014-05-29  9:28         ` James Freer
     [not found] <mailman.2479.1401399676.1147.help-gnu-emacs@gnu.org>
2014-05-29 22:57 ` editor and word processor history (was: Re: RTF for emacs) Emanuel Berg
2014-05-29 23:49   ` Barry Margolin
2014-05-30  1:52   ` Robert Thorpe
     [not found] <mailman.2496.1401414782.1147.help-gnu-emacs@gnu.org>
2014-05-30  2:20 ` Emanuel Berg

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4d71a02-c013-4544-a1dc-4190d496c38d@googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).