From: steve <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Starting a blog on plan 9
Date: Wed, 9 May 2012 19:49:58 +0100 [thread overview]
Message-ID: <D24B278C-DF72-450D-940F-E2A80C09BF05@quintile.net> (raw)
In-Reply-To: <4753aa01-47ee-4945-aa82-9da4691190c3@sm6g2000pbc.googlegroups.com>
in support of sam, i use it and always have, i never
got to the point with acme that it felt worth the effort of changing.
sam is not an an introductory editor, its an alternative.
the one place where i do use acme is the wiki, there is no sam
wiki interface... unless you know different?
On 9 May 2012, at 08:49 AM, IainWS <iainws@gmail.com> wrote:
> On May 9, 6:23 am, yari...@gmail.com (Yaroslav) wrote:
>>> Could you elaborate on your choice of using "sam -d"?
>>
>> Agree, 'sam -d' is not an entry-level choice.
>
> Out of the two editors available I would really opt for using Acme
> instead. If you happen to find yourself newly installing plan 9 then
> someone might suggest Sam to use and you will be stuck trying to learn
> everything about Sam before you can start. Learning only the basics of
> Sam is enough for the new user, and learning it without the mouse
> seems like a really good idea. I agree with you sam -d is not an entry
> level choice, Acme is best for this. In my next post I showed how to
> write hello world in Sam and then suggest Acme for editing files from
> there on.
next prev parent reply other threads:[~2012-05-09 18:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 9:34 IainWS
2012-05-08 10:19 ` Nicolas Bercher
2012-05-08 14:44 ` Tassilo Philipp
2012-05-08 14:51 ` Christoph Lohmann
2012-05-08 15:55 ` Anthony Sorace
2012-05-08 16:15 ` John Floren
2012-05-08 20:23 ` Yaroslav
2012-05-09 8:49 ` IainWS
2012-05-09 8:49 ` IainWS
2012-05-09 18:49 ` steve [this message]
[not found] ` <4753aa01-47ee-4945-aa82-9da4691190c3@sm6g2000pbc.googlegroups.co>
2012-05-09 12:09 ` erik quanstrom
2012-05-09 12:16 ` Russ Cox
2012-05-09 13:27 ` Charles Forsyth
2012-05-09 15:04 ` dexen deVries
2012-05-10 11:35 ` IainWS
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=D24B278C-DF72-450D-940F-E2A80C09BF05@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).