From: Luke Davis <ldavis@voicenet.com>
To: Moe Aitel <aitelm@ase.com>
Cc: blinux-list@redhat.com
Subject: Re: Why I learned emacs was Re: the glass tty model of human-computer interaction
Date: Sat, 19 Dec 1998 17:08:19 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.3.96.981219170643.21448E-100000@unix01> (raw)
In-Reply-To: <3679D507.6F9B@ase.com>
Yes, that would work just as well...
Only one real problem with that: everyone has to build their own.
90 or more % of the people who need it aren't going to want to do it...
But you give me an idea; I'll get with you privately...
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
Richard Uhtenwoldt
` Ann K. Parsons
` wlestes
` Matthew Campbell
` Jude Dashiell
` Charles Hallenbeck
` Dave Mielke
` Lisa Carmelle
` Why I learned emacs was " wlestes
` Dave Mielke
` wlestes
` Moe Aitel
` Luke Davis
` Moe Aitel
` Luke Davis [this message]
` Lar Kaufman
` Why I learned emacs Richard Uhtenwoldt
` Dave Mielke
` Jude Dashiell
` the glass tty model of human-computer interaction wlestes
` Jude Dashiell
` Jude Dashiell
` James H. Cloos Jr.
` Mike Keithley
` Steve Holmes
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=Pine.GSO.3.96.981219170643.21448E-100000@unix01 \
--to=ldavis@voicenet.com \
--cc=aitelm@ase.com \
--cc=blinux-list@redhat.com \
/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).