From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme design
Date: Mon, 7 Jun 2004 08:43:05 -0500 [thread overview]
Message-ID: <ee9e417a0406070643614fb6c2@mail.gmail.com> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D2012D7@XMAIL.asuch.cas.cz>
> could anyone explain me why Edit command (plus the whole language)
> was hardwired into acme (thus breaking its purpose as UI, not an editor,
> and moving closer in spirit to those windozish bloat apps, IMHO)
> instead of a separate prog, like mail was implemented?
> Again, why would be an "acme sam" a bad solution??
> sorry if i am too naive...
You could try using the old edit interface
as described in the acme paper. It was clunky.
Piping things through sed or just running sam
to do what you wanted was much better.
In contrast, I use Edit almost every day, to do
things that you can't do with sed.
Russ
next prev parent reply other threads:[~2004-06-07 13:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 8:22 cej
2004-06-07 13:43 ` Russ Cox [this message]
2004-06-07 13:47 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 11:22 cej
2004-06-04 9:12 cej
2004-06-03 11:21 cej
2004-06-03 14:59 ` a
2004-06-03 8:37 cej
2004-06-03 8:07 cej
2004-06-03 8:52 ` plan9
2004-06-03 13:53 ` rog
2004-06-03 13:55 ` rog
2004-06-05 6:09 ` YAMANASHI Takeshi
2004-06-05 10:07 ` Charles Forsyth
2004-06-05 13:48 ` YAMANASHI Takeshi
2004-06-05 15:50 ` Rob Pike
2004-06-06 2:23 ` YAMANASHI Takeshi
2004-06-06 3:25 ` Rob Pike
2004-06-06 7:24 ` YAMANASHI Takeshi
2004-06-06 8:54 ` vdharani
2004-06-03 7:58 cej
2004-06-03 8:54 ` Kenji Okamoto
2004-06-02 12:57 cej
2004-06-02 13:20 ` a
2004-06-02 15:18 ` plan9
2004-06-03 13:48 ` rog
2004-06-03 14:17 ` lucio
2004-06-03 14:34 ` rog
2004-06-03 15:38 ` kiwane
2004-06-03 15:45 ` rog
2004-06-04 9:19 ` Bengt Kleberg
2004-06-04 10:29 ` Axel Belinfante
2004-06-03 0:54 ` Kenji Okamoto
2004-06-03 0:56 ` Kenji Okamoto
2004-06-03 8:35 ` WLad
2004-06-03 8:40 ` vdharani
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=ee9e417a0406070643614fb6c2@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).