From: Lars Brinkhoff <lars@nocrew.org>
Subject: Re: What the next machine will be like after iMac.
Date: 11 Nov 2003 07:32:48 +0100 [thread overview]
Message-ID: <85znf3ct4f.fsf@junk.nocrew.org> (raw)
In-Reply-To: 3fb076d6$0$56493$1b62eedf@news.wanadoo.nl
Arjan Bos <Arjan.Bos@nospam.ISeeYou.nl> writes:
> Dan Anderson wrote:
> > > The next machines will be Lisp machines with Emacs operating
> > > system running on them.
> > I've been using Emacs as an OS for years and never once looked
> > back. [...] Plus I can customize just about anything I want in
> > LISP. All hail the one true editor!
> So the whole FSF movement and all its GNU tools are created just to
> make the Emacs OS? Interesting direction of thought!
At least Lisp had a prominent role in the original announcement of the
GNU project:
... we plan to have longer filenames, file version numbers, a
crashproof file system, filename completion perhaps, terminal-
independent display support, and eventually a Lisp-based window
system through which several Lisp programs and ordinary Unix
programs can share a screen. Both C and Lisp will be available as
system programming languages.
--
Lars Brinkhoff, Services for Unix, Linux, GCC, HTTP
Brinkhoff Consulting http://www.brinkhoff.se/
next prev parent reply other threads:[~2003-11-11 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 6:35 What the next machine will be like after iMac Don Saklad
2003-11-07 9:05 ` Juri Linkov
2003-11-07 17:29 ` Dan Anderson
[not found] ` <mailman.5.1068233198.2005.help-gnu-emacs@gnu.org>
2003-11-08 7:07 ` Juri Linkov
2003-11-09 18:10 ` Dan Anderson
2003-11-10 7:05 ` Arjan Bos
2003-11-11 6:32 ` Lars Brinkhoff [this message]
2003-11-11 10:28 ` Oliver Scholz
2003-11-07 14:33 ` Tim McNamara
2003-11-07 15:17 ` Stephen H. Westin
2003-11-07 19:50 ` Ola Nilsson
2003-11-07 19:57 ` Barry Margolin
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=85znf3ct4f.fsf@junk.nocrew.org \
--to=lars@nocrew.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).