9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: maht <mattmobile@proweb.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Samterm up down key patch
Date: Tue, 14 Nov 2006 14:42:35 +0000	[thread overview]
Message-ID: <4559D5DB.40407@proweb.co.uk> (raw)
In-Reply-To: <20061114141618.GD11151@shodan.homeunix.net>

Perhaps you long for a line printer and ^j and ^k or have played too
much nethack :)

Using up arrow and down arrow to scroll is IMHO (eventually) a better plan.

Jumping around the text based on the length of the lines and where the
nearest \r is seems odd now.

If I have a long line of wrapped text, pressing down arrow doesn't go
down one line, it goes down one paragraph, Lunix's vi's confusing
jumping cursor should tell you that.

YMMV of course.

But please, and I'm sure no-one will, don't change the cursor keys in Acme.

And while you discuss it, don't forget that Home and End are also
different in plan9 in that they refer to the document not the current line.

matt







  reply	other threads:[~2006-11-14 14:42 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 [this message]
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

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=4559D5DB.40407@proweb.co.uk \
    --to=mattmobile@proweb.co.uk \
    --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).