9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] Samterm up down key patch
Date: Tue, 14 Nov 2006 10:03:00 -0800	[thread overview]
Message-ID: <3e1162e60611141003l4e113cd6x5aa594cd5c2482f0@mail.gmail.com> (raw)
In-Reply-To: <13426df10611140525k68c31de1s525c816957352836@mail.gmail.com>

On 11/14/06, ron minnich <rminnich@gmail.com> wrote:
> On 11/14/06, Martin Neubauer <m.ne@gmx.net> wrote:
> > Hello,
> >
> > I'm not quite convinced of the merit of that behaviour. The most direct
> > consequence is that it makes sam inconsistent with acme and rio windows.
>
> But maybe rio and acme are wrong.
>
> I guess we can worry about internal consistency in plan 9, but fact
> is, in the rest of the known universe, uparrow goes up a line,
> downarrow goes down, they move the cursor.
>
> We've got page up and page down; we could always use them. It was bad
> enough when right arrow and left arrow did what they did ....
>
> If we're halfway to readline, well, then, maybe people want it, and we
> should have it, and not having it was a mistake all along.  You should
> be different if it makes sense; otherwise, don't.
>
> But the worst thing we can do is fall into the 'it's always worked
> this way' mantra. At that point, you might as well be a Fortran
> programmer.

But isn't that just what you're saying?  You're used to the way
everyone else does everything, so therefore this new way is wrong?  My
original PCs didn't have mice, and I really don't think the first
mouse intefaces I had on DOS were that good.

What Acme does with the mouse is a big step from what any other editor
I've used has tried to do with it, in terms of the clickable text,
chord-based editing and the way it makes you think differently about
the keyboard.

I agree it takes a good deal of discipline to learn to use acme the
way it is effectively if you come from a different background, and I'm
by no means an expert (see my winclear script... :-) ) but I'm trying
to learn it the way it was meant to be used, and I find surprises that
make me wish Emacs were more like it sometimes.  (especially in
simplicity)

However, it's very clear that people are always going to want to morph
Sam and Acme into the editor they're used to, so why doesn't someone
either fork it, or make some editors that are more familiar to these
folks.  Acme will still be useful to those who know it, and there will
probably always be an Acme community or is there fear of the loss of
that too?

>
> ron
>


      parent reply	other threads:[~2006-11-14 18:03 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14  1:02 Joey Makar
2006-11-14 10:49 ` Martin Neubauer
2006-11-14 13:04   ` erik quanstrom
2006-11-14 13:26     ` Martin Neubauer
2006-11-14 13:38       ` erik quanstrom
2006-11-14 18:04         ` David Leimbach
2006-11-14 13:25   ` ron minnich
2006-11-14 13:34     ` erik quanstrom
2006-11-14 13:44       ` ron minnich
2006-11-14 14:04         ` erik quanstrom
2006-11-14 14:16         ` Martin Neubauer
2006-11-14 14:42           ` maht
2006-11-14 16:48             ` Joel Salomon
2006-11-14 17:03               ` maht
2006-11-14 16:48             ` Joey Makar
2006-11-14 20:03             ` John Floren
2006-11-14 21:57               ` Russ Cox
2006-11-14 22:06                 ` David Leimbach
2006-11-15  9:40               ` Matt
2007-01-30  9:55               ` Harri Haataja
2007-01-30 11:34                 ` John Stalker
2006-11-14 18:10         ` David Leimbach
2006-11-14 18:21           ` Sape Mullender
2006-11-14 18:35             ` erik quanstrom
2006-11-14 18:52               ` Bruce Ellis
2006-11-14 19:14                 ` Sape Mullender
2006-11-14 19:18                   ` Paul Lalonde
2006-11-14 19:34                 ` rog
2006-11-14 19:40                   ` csant
2006-11-14 19:52                     ` Bruce Ellis
2006-11-14 18:22           ` Bruce Ellis
2006-11-15  4:43       ` Lyndon Nerenberg
2006-11-15  4:57         ` John Floren
2006-11-15  5:13           ` Russ Cox
2006-11-15  5:32             ` John Floren
2006-11-15  9:27               ` Gorka guardiola
2006-11-15 14:09             ` David Arnold
2006-11-16  2:49             ` erik quanstrom
2006-11-16 13:46               ` plan9
2006-11-16 13:55                 ` Abhey Shah
2006-11-17 16:44                 ` erik quanstrom
2006-11-20  5:48             ` Noah Evans
2007-01-30 11:28             ` Harri Haataja
2007-01-30 11:35               ` Russ Cox
2007-01-30 11:45                 ` Gabriel Diaz
2006-11-15  5:28         ` Lyndon Nerenberg
2006-11-15 16:26           ` David Leimbach
2006-11-14 14:08     ` Martin Neubauer
2006-11-14 14:20     ` Wes Kussmaul
2006-11-14 15:07       ` Wes Kussmaul
2006-11-14 18:03     ` David Leimbach [this message]

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