9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J. R. Mauro" <jrm8005@gmail.com>
To: "corey@bitworthy.net" <corey@bitworthy.net>,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: "9fans@9fans.net" <9fans@9fans.net>
Subject: Re: [9fans] first timer - editing plan9.ini
Date: Wed, 22 Jul 2009 14:09:53 -0400	[thread overview]
Message-ID: <A229E43F-3F5E-40F8-BCFE-3F865D4B0BBE@gmail.com> (raw)
In-Reply-To: <200907191929.49163.corey@bitworthy.net>





On Jul 19, 2009, at 22:29, Corey <corey@bitworthy.net> wrote:

> On Sunday 19 July 2009 19:12:50 Skip Tavakkolian wrote:
>>> The few minutes spent learning ed(1) will be well repaid. You'll be
>>> one of the smartest guys on your block.
>>
>> i second that.  learning it has been one of the best investments of
>> my
>> time since 1982.
>>
>
> <grin>
>
> I would say the same thing about vi, which I practically live in,
> and feel
> hamstrung without.
>
> At anyrate, I do intend on sitting down and becoming at least
> comfortable
> with sam's ed.
>
> Though I'm guessing that I'll be installing Stefan's vim port asap -
> I'm
> _extremely_ happy that this exists.

It's sad to see people recommending acme instead of helping a bit with
Sam. You should try both, and use what fits you. I like Sam because it
is just an editor. Acme is more of a platform for making tools
interact, and to me ends up feeling like a swiss army chainsaw. I've
left vi behind because I learned Sam, and maybe you'll like it enough
to switch, too.

Until you get proficient in Sam, using the right-button menu will give
you the file-related commands you need, and / and s in the command
window will do until you learn the more powerful Sam commands and
idioms.

To get more proficient, I highly recommend Rob's paper 'A Tutorial For
The Sam Command Language' and the Sam reference card, which show you
the idioms for using Sam more effectively and give you a glimpse of
it's power. It helps if you read them more than once.

Good luck, I hope you find Sam or Acme to your liking :)

>
> http://vmsplice.net/9vim.html
>
>
> Cheers
>
>



  reply	other threads:[~2009-07-22 18:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 22:51 Corey
2009-07-19 22:58 ` hiro
2009-07-19 23:02 ` John Floren
2009-07-19 23:19   ` Corey
2009-07-19 23:25     ` John Floren
2009-07-19 23:35       ` erik quanstrom
2009-07-20  0:08       ` Corey
2009-07-19 23:28     ` Federico G. Benavento
2009-07-19 23:30       ` erik quanstrom
2009-07-19 23:04 ` Brantley Coile
2009-07-19 23:18   ` Corey
2009-07-20  2:12   ` Skip Tavakkolian
2009-07-20  2:29     ` Corey
2009-07-22 18:09       ` J. R. Mauro [this message]
2009-07-24 10:49       ` maht
     [not found]         ` <4B03FCAB-BFF1-483F-BCF8-369F0E6711C9@gmail.com>
2009-07-24 18:05           ` Rodolfo (kix)
2009-07-24 19:18             ` David Leimbach
2009-07-25  9:56         ` Ethan Grammatikidis
2009-07-20 14:40     ` David Leimbach
2009-07-20  2:50 ` Jason Catena
2009-07-20  3:10 ` Lyndon Nerenberg

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=A229E43F-3F5E-40F8-BCFE-3F865D4B0BBE@gmail.com \
    --to=jrm8005@gmail.com \
    --cc=9fans@9fans.net \
    --cc=corey@bitworthy.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).