9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Chords, ^, _, ^B and scroll with mouse wheel in p9p sam
Date: Fri, 27 May 2016 23:16:07 +0100	[thread overview]
Message-ID: <1464387367.1179524.620989337.0120C4D1@webmail.messagingengine.com> (raw)
In-Reply-To: <CAK-yzPO5CikBL5vSw3OX04xZTcFHWCkasG1-PZ6COfczNP0W=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Fri, May 27, 2016, at 09:57 PM, Mark Lee Smith wrote:
> Thanks for sharing this! I'd already backported a few of the features,
> but I hadn't yet got around to looking at the chording code etc. It's
> great to have selection working! I'm not sure if I did something wrong
> (I've checked the changes a few times) but scrolling only works
> "sometimes", mostly it seems to get stuck when scrolling back up? Can
> anyone confirm? In my experience sam's scrolling seems to be pretty
> broken (at least in the plan9port version) so it might not have
> anything to do with these changes.

Welcome to the club. *hands you your "I have experienced
samscrolling" badge*

"Samscrolling" refers to scrolling by cursor keys; you didn't say keys,
scrollbar, or scroll wheel. Samscrolling is something of a phenomenon in
its own right. 9front added another, more predictable but scarcely more
controllable phenomenon which applies to the scroll wheel: The nearer
the mouse pointer is to the bottom of the window, the more effective the
scroll wheel is, until at the bottom one notch on the wheel moves a
whole page. I call this feature TURBO ULTRADRIVE HYPERSCROLLING because
for those of us with real scroll wheels and too focused on the actual
text to remember where the mouse pointer is, it's fantastically
annoying. They inflicted it on rio too, months ago, and I'm still not
entirely used to it. The one guy who loves this feature uses that IBM
mouse with a trackpoint instead of a scroll wheel.

I'm too old to use vi.

[-- Attachment #2: Type: text/html, Size: 2095 bytes --]

  parent reply	other threads:[~2016-05-27 22:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 22:03 trebol55555
2016-05-27 20:57 ` Mark Lee Smith
2016-05-27 21:42   ` Tobias Kreisel
2016-05-27 22:16   ` Ethan Grammatikidis [this message]
2016-05-27 22:37     ` stanley lieber
2016-05-28 15:25       ` Ethan Grammatikidis
2016-05-27 23:09     ` Kurt H Maier
2016-05-27 17:11 trebol55555
2016-05-27 17:46 ` Mark Lee Smith
2016-05-27 18:04   ` trebol55555
2016-05-28 10:04     ` Mark Lee Smith
2016-05-30 16:35 trebol55555
2016-05-31  1:34 trebol55555

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1464387367.1179524.620989337.0120C4D1@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --cc=9fans@9fans.net \


* 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).