9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
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 08:16:12 -0400	[thread overview]
Message-ID: <CADSkJJXsBY1f7dVf_MWNTdPO5ebdtdYU8cdKoT24eYnEZqZahA@mail.gmail.com> (raw)
In-Reply-To: <0cc5d7ea7f1e905bd7fefa5515869e1a@kw.quanstro.net>

On Wed, May 9, 2012 at 8:09 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> 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

I think it's much easier to learn sam _with_ the mouse, and only then
move on to sam -d for times when just want the typescript window and
not to look at any of the files.  "sam -d" is really not an editor for
beginners.  For the kind of minor editing that you're explaining in
your blog post, I can't think of a single reason to reach for "sam -d"
instead of "ed", but it would be more common to start acme or plain
sam instead.  It's not like Eclipse where you have to wait minutes for
the thing to start.

Russ


  reply	other threads:[~2012-05-09 12:16 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
     [not found] ` <4753aa01-47ee-4945-aa82-9da4691190c3@sm6g2000pbc.googlegroups.co>
2012-05-09 12:09   ` erik quanstrom
2012-05-09 12:16     ` Russ Cox [this message]
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=CADSkJJXsBY1f7dVf_MWNTdPO5ebdtdYU8cdKoT24eYnEZqZahA@mail.gmail.com \
    --to=rsc@swtch.com \
    --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).