9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] command repetition in sam/acme
Date: Tue,  3 Mar 2009 18:19:29 -0500	[thread overview]
Message-ID: <3aaafc130903031519t1408bfcmb98c7d2cfb66433a@mail.gmail.com> (raw)
In-Reply-To: <13426df10903031413n13e53b8bxef266c2551aa8abd@mail.gmail.com>

On Tue, Mar 3, 2009 at 5:13 PM, ron minnich <rminnich@gmail.com> wrote:
> This discussion strikes me as coming from a different galaxy. It seems
> to me that Acme and Sam clearly don't match the task at hand. We're
> trying to use a screwdriver when we need a jackhammer .
>
> I don't see the point in complaining about file formats. The
> scientists in this case don't much care what we think. They're not
> going to rewrite their formats so someone can use Acme.
>
> Here's my suggestion:
>
> vi

I seem to remember an interview with Rob Pike where he said that the
reason he hated vi and emacs was that they didn't support mouse
placement, and other than that, they were fine. I wonder if he would
find Vim usable these days, given that you can mouse around in it
without sacrificing the really powerful command syntax that Rudolf
seems to be missing here.

It's definitely efficient to be able to just "point and say 'here'",
which I think is the wording Rob used, but it's also useful to be able
to just say "go down 5 lines and then forward 5 words", which vi
excels at. I really like Acme, but (and maybe it's just me being a
newbie) I find myself really missing some of the vi
movement/delete/yank syntax.



Just my $.02 USD, which, due to inflation, is pretty worthless these days.

>
> ron
>
>



  reply	other threads:[~2009-03-03 23:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 12:07 Rudolf Sykora
2009-03-03 12:49 ` Steve Simon
2009-03-03 13:53   ` Rudolf Sykora
2009-03-03 15:40     ` roger peppe
2009-03-03 15:58       ` yy
2009-03-03 16:25         ` Rudolf Sykora
2009-03-03 15:58       ` Uriel
2009-03-03 15:59         ` Uriel
2009-03-03 14:15 ` John Stalker
2009-03-03 14:23   ` Rudolf Sykora
2009-03-03 16:09 ` Russ Cox
2009-03-03 16:31   ` roger peppe
2009-03-03 17:16     ` Uriel
2009-03-03 18:50       ` Rudolf Sykora
2009-03-03 16:39   ` Rudolf Sykora
2009-03-03 20:30   ` Arvindh Rajesh Tamilmani
2009-03-03 22:13     ` ron minnich
2009-03-03 23:19       ` J.R. Mauro [this message]
2009-03-03 23:37       ` Anthony Sorace
2009-03-04  0:31         ` Rob Pike
2009-03-04  0:44           ` J.R. Mauro
2009-03-04  0:56             ` Rob Pike
2009-03-04  1:51               ` J.R. Mauro
2009-03-04  2:15                 ` Rob Pike
2009-03-04  4:59                   ` J.R. Mauro
2009-03-04  9:41           ` Rudolf Sykora
2009-03-04  9:52             ` Rob Pike
2009-03-04 11:32               ` Rudolf Sykora
2009-03-04 13:31                 ` Uriel
2009-03-04 13:41                   ` Rudolf Sykora
2009-03-04 16:35                   ` John Stalker
2009-03-04 16:56                     ` ron minnich
2009-03-04 13:37             ` erik quanstrom
2009-03-04 14:14               ` Rudolf Sykora
2009-03-04 14:37                 ` erik quanstrom
2009-03-04 14:59                   ` Rudolf Sykora
2009-03-04 16:34                 ` Steve Simon
2009-03-04 17:03             ` Russ Cox

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=3aaafc130903031519t1408bfcmb98c7d2cfb66433a@mail.gmail.com \
    --to=jrm8005@gmail.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).