From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
Date: Mon, 10 Jun 2002 11:31:33 +0100 [thread overview]
Message-ID: <34052a07e5069d62d92e53f5546f1ade@9fs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
I perhaps should have been a bit clearer that understanding the
philosphy is vital, and reading the documents is the only way at the
moment. This is not optimal I accept.
You cannot roll up to Plan 9 and use it on the assumption that it
provides a standard Unix environment, with some extra goodies. Plan 9
is package; you have to work in a different way to get the benefit.
As I switch between many development environments in my work, I know
the good and bad bits of all the options. I wouldn't be working with
Plan 9 if I didn't percieve a benefit.
If your only requirements are a C compiler and an editor, and you have
a project to do, then to justify Plan 9 as the development environment
you must use it in the way it is designed to be used.
That, at the moment, will require some reading around. I can see that
if familiar tools were available you might be able to get your work
done in a traditional way, while soaking up some of the 'culture' of
Plan 9, without losing too much time, but unfortunately that's not an
option.
[-- Attachment #2: Type: message/rfc822, Size: 1901 bytes --]
From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
Date: Mon, 10 Jun 2002 11:10:08 +0100
Message-ID: <20020610101000.F2D4219991@mail.cse.psu.edu>
sam is by no means `like notepad'. i've used both. sam is the older
of the two visual editors, and the newer one, acme, includes the
more powerful features of sam (notably structural regular expressions
and the editing command structure) but is an environment
(with a significant nod to Oberon) that is closer in functionality
to emacs but with a different approach to integrating new functions
such as multi-file editing, mail, news, wiki, and other things.
it would be helpful if there were a more tutorial introduction to acme
i suppose, but have a look at the paper, not just the manual page.
similarly, what can be done with the Edit verb is probably not by
any means obvious, so it's not surprising you concluded as you did.
next reply other threads:[~2002-06-10 10:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 10:31 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-12 17:56 anothy
2002-06-12 9:18 nigel
2002-06-12 9:07 forsyth
2002-06-12 10:08 ` John Murdie
2002-06-13 9:29 ` Don
2002-06-12 7:49 Fco.J.Ballesteros
2002-06-11 10:08 forsyth
2002-06-12 8:54 ` Don
2002-06-10 10:31 nigel
2002-06-10 10:21 Fco.J.Ballesteros
2002-06-10 10:10 forsyth
2002-06-07 9:35 nigel
2002-06-10 9:53 ` Blake McBride
2002-06-10 17:00 ` Steve Kilbane
2002-06-11 9:08 ` Don
2002-06-11 18:55 ` Vladimir G. Ivanovic
2002-06-12 8:54 ` Don
2002-06-11 9:09 ` Douglas A. Gwyn
2002-06-10 10:02 ` Douglas A. Gwyn
2002-06-10 14:10 ` Blake McBride
2002-06-10 17:13 ` Quinn Dunkan
2002-06-10 18:15 ` Fariborz Tavakkolian
2002-06-10 20:43 ` FJ Ballesteros
2002-06-11 9:08 ` Don
2002-06-11 9:09 ` Douglas A. Gwyn
2002-06-12 8:54 ` Joel Salomon
2002-06-10 15:47 ` James A. Robinson
2002-06-11 15:27 ` Blake McBride
2002-06-11 17:36 ` Digby Tarvin
2002-06-11 17:44 ` James A. Robinson
2002-06-11 20:43 ` Digby Tarvin
2002-06-07 9:06 Blake McBride
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=34052a07e5069d62d92e53f5546f1ade@9fs.org \
--to=nigel@9fs.org \
--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).