From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: editor and word processor history
Date: Fri, 30 May 2014 06:06:09 +0200 [thread overview]
Message-ID: <87wqd37vwu.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 8738fsatxy.fsf@debian.uxu
Emanuel Berg <embe8573@student.uu.se> writes:
> Robert Thorpe <rt@robertthorpeconsulting.com> writes:
>
>> Programs were typed in using keypunches which wrote
>> to punched cards or using devices that wrote to paper
>> tape. The program was then submitted as a stack of
>> cards or a tape to the sysadmins who ran the
>> computer. The computer would then "SPOOL" copying
>> the paper information to magnetic tape where it could
>> be accessed later. Once that happened the user could
>> do various things like edit the code, compile it and
>> so on.
>>
>> This meant there was a delay between the user's
>> information being sent and the program execution.
>> Often in that time errors could be found. In that
>> case the user could run an editor from a teletype and
>> fix the errors. Doing that wouldn't necessarily
>> require the teletype to print out each line of code
>> being changed. That's why in early editors there
>> were commands to print out lines of code, but things
>> could be done without them.
>>
>> This was all high technology compared to the early
>> days when everything submitted on cards was compiled
>> and executed without question. In those early days
>> there were no editors. Everything depended on
>> punched cards and there were special machines to deal
>> with them which were a partial substitute. (Even in
>> the 1970s most small IBM computers were only sold
>> with peripheral for reading and punching cards.)
>
> I suppose this would be a lot easier to understand if
> you could actually see (and touch) the machines. I have
> heard that in the US (Boston and San Francisco) there
> are computer museum, sometimes associated with the
> companies themselves.
You can always use simulators:
http://www.masswerk.at/google60/
Otherwise, it wouldn't be too hard to configure emacs to reproduce the
feel and constraints of software development in the 60s or 70s.
M-x caps-mode RET
M-x computer-paper RET (https://gitorious.org/com-informatimago/emacs/source/master:pjb-computer-paper.el)
--
__Pascal Bourguignon__
http://www.informatimago.com/
"Le mercure monte ? C'est le moment d'acheter !"
next prev parent reply other threads:[~2014-05-30 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2496.1401414782.1147.help-gnu-emacs@gnu.org>
2014-05-30 2:20 ` editor and word processor history (was: Re: RTF for emacs) Emanuel Berg
2014-05-30 4:06 ` Pascal J. Bourguignon [this message]
2014-06-01 0:07 ` editor and word processor history Emanuel Berg
2014-05-25 19:24 RTF for emacs Robert Thorpe
[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 7:23 ` editor and word processor history Glyn Millington
[not found] ` <mailman.2380.1401356412.1147.help-gnu-emacs@gnu.org>
2014-05-29 12:32 ` Haines Brown
[not found] ` <mailman.2376.1401348837.1147.help-gnu-emacs@gnu.org>
2014-05-29 23:51 ` 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=87wqd37vwu.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.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).