9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Chris Locke" <chris@cjl1.demon.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] home, end ^h^j^k^l
Date: Fri, 18 May 2001 20:26:34 +0100	[thread overview]
Message-ID: <001701c0dfd0$82f59ca0$2248dec2@falken> (raw)
In-Reply-To: <9866732295.20010518111829@proweb.co.uk>

One thing in acme that quite often bites me is the tendency when
chording a cut for the cursor to drop onto the line below and cut
much more than I intended.

I must have a tendency of keeping the cursor close to the bottom of
the line when making a selection. The action of chording the middle
button is often enough to drop the cursor down a fraction onto the
lower line, just as the cut is done.

One thing that would make this much less likely to happen was if there
were some hysteresis in selecting across lines. i.e. the selection
would only extend into another line when the cursor had moved a
few pixels vertically into it.

Perhaps I should just be more careful!

What are other peoples most common acme 'gotchas'?

Cheers,
Chris.




  reply	other threads:[~2001-05-18 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 10:18 Matt H
2001-05-18 19:26 ` Chris Locke [this message]
2001-05-18 19:34   ` Scott Schwartz
2001-05-19  7:54   ` Re[2]: " Matt H
2001-05-19 17:07     ` Quinn Dunkan
2001-05-19 16:00       ` Re[4]: " Matt H
2001-05-19 20:46         ` Boyd Roberts
2001-05-21 16:24           ` Douglas A. Gwyn
2001-05-21 16:23       ` Douglas A. Gwyn
2001-05-19 20:19     ` Re[2]: " Boyd Roberts
2001-05-18 22:28 ` Boyd Roberts
2001-05-18 15:17 Russ Cox
2001-05-21  8:38 ` Douglas A. Gwyn
2001-05-18 20:23 rog
2001-05-19 15:39 Re[4]: " rob pike
2001-05-21 16:24 ` Douglas A. Gwyn
2001-05-22  6:25 nemo
2001-05-22  6:35 ` Scott Merrilees
2001-05-22  8:31 ` Boyd Roberts
2001-05-22  7:17 nemo
2001-05-22 12:36 rob pike
2001-05-22 14:42 nemo

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='001701c0dfd0$82f59ca0$2248dec2@falken' \
    --to=chris@cjl1.demon.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).