From: Drew Adams <drew.adams@oracle.com>
To: Hikaru Ichijyo <ichijyo@macross.sdf.jp>, help-gnu-emacs@gnu.org
Subject: RE: launch a program in an arbitrary frame
Date: Sat, 18 Jul 2015 15:45:18 -0700 (PDT) [thread overview]
Message-ID: <3e07a3bc-bd5a-42f7-b048-4083021ba6b1@default> (raw)
In-Reply-To: <8xxa8utdsof.fsf@village.keycorner.org>
> Generally, I just meant that I remember in the 1980's and 90's, people
> used to joke about Emacs being enormous. On 80's workstations, it might
> take all the memory in your machine just to run an Emacs session.
Do you remember Emacs being a memory hog back then, or do you just
remember hearing someone joke about it that way?
FWIW, I used Emacs heavily back then, on Unix workstations, Lisp
machines, and terminals (UNIX, VAX/VMS). I never found it to be
a memory hog or sluggish or bloated. Clearly, Emacs was smaller
back then too, but I've never noticed it being particularly slow.
Certainly, no one I knew ever had the impression that it "might
take all the memory in your machine just to run an Emacs session."
My recollection tells me that's a wild fairy tale. Early PCs were
limited (and didn't run Emacs), but not workstations.
I even used Emacs sometimes on a very limited baud stream over a
phone line, where you often had to fiddle with `C-l' (to refresh,
slowly, top to bottom - like watching a Surveyor image arrive from
an early moon landing) and scroll locking. In that context, yes,
the slow response could be a pain, but that was the wire, not Emacs
- anything "interactive" over such a wire was slow.
Of course, for someone used to `vi' and starting up the editor
each time even to change only a few chars, Emacs was, and is,
slow to start and use, by comparison. But such comparisons have
always been essentially apples-to-oranges.
next prev parent reply other threads:[~2015-07-18 22:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 3:21 launch a program in an arbitrary frame Hikaru Ichijyo
2015-07-18 4:12 ` Vaidheeswaran C
2015-07-18 8:29 ` Emanuel Berg
2015-07-18 4:18 ` Vaidheeswaran C
2015-07-18 5:22 ` Drew Adams
2015-07-18 8:14 ` Emanuel Berg
[not found] ` <mailman.7087.1437207364.904.help-gnu-emacs@gnu.org>
2015-07-18 15:53 ` Hikaru Ichijyo
2015-07-18 16:35 ` Eli Zaretskii
2015-07-18 17:06 ` Óscar Fuentes
[not found] ` <mailman.7100.1437237353.904.help-gnu-emacs@gnu.org>
2015-07-18 17:12 ` Hikaru Ichijyo
2015-07-18 19:26 ` Emanuel Berg
[not found] ` <mailman.7109.1437247711.904.help-gnu-emacs@gnu.org>
2015-07-18 22:09 ` Hikaru Ichijyo
2015-07-18 22:45 ` Drew Adams [this message]
[not found] ` <mailman.7117.1437259681.904.help-gnu-emacs@gnu.org>
2015-07-18 23:28 ` Hikaru Ichijyo
2015-07-18 23:47 ` Emanuel Berg
[not found] ` <mailman.7122.1437263415.904.help-gnu-emacs@gnu.org>
2015-07-19 0:03 ` Hikaru Ichijyo
2015-07-19 0:32 ` Drew Adams
2015-07-19 7:15 ` Emanuel Berg
2015-07-19 13:03 ` Drew Adams
[not found] ` <mailman.7140.1437290215.904.help-gnu-emacs@gnu.org>
2015-07-19 10:40 ` Pascal J. Bourguignon
[not found] ` <mailman.7101.1437239201.904.help-gnu-emacs@gnu.org>
2015-07-18 17:47 ` Hikaru Ichijyo
2015-07-18 19:18 ` Emanuel Berg
[not found] ` <mailman.7108.1437247198.904.help-gnu-emacs@gnu.org>
2015-07-18 22:01 ` Hikaru Ichijyo
2015-07-18 22:56 ` Emanuel Berg
2015-07-18 23:39 ` Emanuel Berg
[not found] ` <mailman.7120.1437262864.904.help-gnu-emacs@gnu.org>
2015-07-18 23:51 ` Hikaru Ichijyo
2015-07-18 23:58 ` Emanuel Berg
[not found] ` <mailman.7124.1437264614.904.help-gnu-emacs@gnu.org>
2015-07-19 0:55 ` Hikaru Ichijyo
[not found] ` <mailman.7118.1437260312.904.help-gnu-emacs@gnu.org>
2015-07-18 23:32 ` Hikaru Ichijyo
2015-07-18 23:42 ` 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=3e07a3bc-bd5a-42f7-b048-4083021ba6b1@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=ichijyo@macross.sdf.jp \
/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).