9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text editor
Date: Fri, 26 Apr 2002 13:31:21 -0400	[thread overview]
Message-ID: <d2e5ce5f47a5595314dfe7882ca737a6@plan9.bell-labs.com> (raw)

the part that is painful is, as rog said, the differences
and inconsistencies.  every time you try to do something
and wily doesn't quite behave the same way, it hurts.

the most notable one is the different handling of
Put when the file has been changed underneath you.
i realize this was a design decision, but it's just
weird when you're used to the acme behavior.
and if you don't know how to use the wilybak
directory (which i don't, really) then it's hard
to get the file back.

another difference is the behavior of arrow keys.
in acme, if i type an up or down arrow, the screen
scrolls up or down half a page.  in wily, if i type one
of the arrow keys, the cursor moves!  if i wanted
to move the cursor, i would have clicked somewhere
with the mouse like god, rob, and tog intended.

of course, plan 9 didn't have arrow keys when wily
started, and so wily and acme have separately defined
meaning for them.  but it's unfortunate that wily caved
to the keystrokes-for-positioning factions.

it also bothers me that wily is so much less dense
than acme as far as fitting things on the screen.
there's far too much white space above and below the
text in the tag lines.

it's the little things.  wily is still my choice
of editor for unix.  it just annoys me when i use it.



             reply	other threads:[~2002-04-26 17:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 17:31 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-29  9:36 Andrew Simmons
2002-04-26 14:52 anothy
2002-04-26 16:59 ` peter huang
2002-04-26 14:10 Russ Cox
2002-04-26 10:27 ` Sam Hopkins
2002-04-29  9:40 ` Douglas A. Gwyn
2002-04-26 13:40 forsyth
2002-04-26 13:27 presotto
2002-04-26 12:46 bwc
2002-04-26 16:33 ` mcguire
2002-04-30  1:54   ` chad
2002-04-26 12:40 nigel
2002-04-26 11:41 forsyth
2002-04-26 11:39 rog
2002-04-26 11:45 ` Boyd Roberts
2002-04-26 10:45 nigel
2002-04-26 11:04 ` Alexander Viro
2002-04-26 10:22 nigel
2002-04-26 11:15 ` Boyd Roberts
2002-04-26 11:25   ` Boyd Roberts
2002-04-26 16:06   ` Ronald G Minnich
2002-04-26 10:11 rog
2002-04-26 23:30 ` Micah Stetson
2002-04-26  9:49 nigel
2002-04-26 10:21 ` Alexander Viro
2002-04-26 11:38   ` Michael Grunditz
2002-04-26 20:35   ` Dan Cross
2002-04-29  9:40     ` Douglas A. Gwyn
2002-04-29  9:36 ` Andrew Stitt
2002-04-29 15:58   ` Douglas A. Gwyn
2002-04-26  8:47 Andrew Stitt

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=d2e5ce5f47a5595314dfe7882ca737a6@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).