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 20:01:26 +0100	[thread overview]
Message-ID: <a560a5d01001231101r6b5fc408gef4a8aa69d81ed09@mail.gmail.com> (raw)
In-Reply-To: <b581a310ecd9daedd9b4e9e6b4b23b43@bellsouth.net>

> Maybe it only
> happens once in 1000 times, but in that 0.1% of the time, my
> finger coming down on the return key accidentally hits the up
> arrow and the timing just so happens that I rerun the previous
> command instead of the one I just typed, sometimes with very
> unpleasant consqeuences.

This is the 1st time I hear about such a misfortune... :)

> As for up-arrow moving up a line, this comes up from time to
> time.  It's primary usefulness is in editors.  But in a proportional
> font, what exactly does moving up a line mean?  Move to the
> position that is the same number of characters from the beginning
> of the line?  Move to the same geometric position?  What if that
> position is in the middle of a character?  No one ever seems to
> float a proposal that hits everyone as having "the ring of truth."
> I have thought there could be some usefulness in this, but I
> haven't thought of a policy that is so beautiful it draws me to
> the source to code it.

All usual editors that use proportional fonts have to cope with this somehow.
E.g. one of the most common in linux, openoffice's writer, seems to be
trying to move the cursor approximately to the same geometric
position.

R



  reply	other threads:[~2010-01-23 19:01 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
2010-01-23 13:07   ` Yi DAI
2010-01-23 17:13   ` blstuart
2010-01-23 19:01     ` Rudolf Sykora [this message]
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=a560a5d01001231101r6b5fc408gef4a8aa69d81ed09@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).