9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Shall we fix the use of Up/Dn arrows?
Date: Sat, 23 Jan 2010 13:52:47 +0100	[thread overview]
Message-ID: <a560a5d01001230452p35494b9fle8b10223b8045861@mail.gmail.com> (raw)
In-Reply-To: <7aee91501001230115q5285b2ebyd2df99db84f6855d@mail.gmail.com>

> 1. We use Lf/Rt arrows to move the cursor, don't we? Then use Up/Dn to do the same kind of task is symmetric, and thus more reasonable.

In case of being in an editor, editing some text, I'd say your idea
has a point. Also I find it disturbing when instead of moving up one
line the scrolling comes instead.
On the other hand, being in a rio window or an acme win window, moving
the cursor up or down using the arrows doesn't have much sense (in any
case you have to use a mouse to do something useful with a text
there).

What I'd appreciate, from the user's point of view, would be some kind
of history mechanism tied to the up/down keys in rio/win (where I
interact with a shell), up arrow bringing up the last command e.g.,
and a normal movement behaviour when editing a 'text' file (no direct
interaction with the shell, where 'enter' is just a newline).
On the other hand, implementing such a mechanism would probably lead
to ugly complications, which might be better be avoided. For now,
simplicity wins.

Btw., I know the " and "" scripts by R Cox, I use them. Without
something like them, it would be hell. Anyhow, hitting the up/down key
a few times is just quicker.

R



  parent reply	other threads:[~2010-01-23 12:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23  9:15 Yi DAI
2010-01-23  9:35 ` Akshat Kumar
2010-01-23  9:59 ` Bela Valek
2010-01-23 10:21 ` John Stalker
2010-01-23 14:29   ` Patrick Kelly
2010-01-23 12:37 ` cinap_lenrek
2010-01-23 12:52 ` Rudolf Sykora [this message]
2010-01-23 13:07   ` Yi DAI
2010-01-23 17:13   ` blstuart
2010-01-23 19:01     ` Rudolf Sykora
2010-01-25 17:20       ` maht
2010-01-26 11:50         ` Rudolf Sykora
2010-01-26 12:26           ` yy
2010-01-26 12:34           ` Robert Raschke
2010-01-26 14:16             ` erik quanstrom
2010-01-23 19:10 ` Russ Cox
2010-01-23 19:25   ` Rudolf Sykora
2010-01-24  0:53     ` Russ Cox
2010-01-24  7:08 ` Frederik Caulier
2010-01-24  9:08   ` Yi DAI
2010-01-24 18:03 ` Tim Newsham
2010-01-24 22:28   ` Charles Forsyth
2010-01-24 18:41 ` John Floren
2010-01-25  9:46 ` Pavel Klinkovsky

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=a560a5d01001230452p35494b9fle8b10223b8045861@mail.gmail.com \
    --to=rudolf.sykora@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).