9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] rio: resize flash patch
Date: Sun, 29 Nov 2020 21:17:29 -0500	[thread overview]
Message-ID: <A835C1C4-7340-4D5D-A0F9-F8839C71CB98@stanleylieber.com> (raw)
In-Reply-To: <C2552894E92CD4634A749AD40EDDBA61@eigenstate.org>

On November 29, 2020 8:48:46 PM EST, ori@eigenstate.org wrote:
>Quoth Alex Musolino <alex@musolino.id.au>:
>> 
>> Yeah, it *was* added for a time (changeset d0a53c92a84d) but later removed
>> because it caused some problems (changeset a43c3e5624da). For what it's worth,
>> I happen to like the ability to vary the stride of a scroll wheel click.  I'd
>> like to see this feature in acme.
>
>Agreed, I like it too. Also: The distance down the window controls the speed
>of scrolling everywhere else.
>
>But I get it -- it's definitely something that threw me off until I realized
>what was actually going on. If you don't know what changes scroll speed, having
>things scroll half a page at a time sometimes, but only a line at a time at
>other times can be disorienting.

galaxy brain scrolling was my idea (although i didn't implement it). it's also in sam and mothtra. i urged for it to br added to acme, and it was, but as alex mentioned, the implementation was broken so it was removed. it works just like clicking at different places in the scrollbar, only it's with the scrollwheel used anywhere. to me, it makes scrolling more intuitive and efficient.

shift+scroll for one line at a time (currently implemented only in rio) was likewise my idea. i think cinap actually implemented that one. i wanted it elsewhere, too, but it's more complicated in other privrams.

coincidentally i'm working on an update to fqa8 that explains all the currently extant scrolling quirks.

sl

  reply	other threads:[~2020-11-30  2:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22  4:36 Amavect
2020-11-22  5:33 ` [9front] " ori
2020-11-22  6:18   ` Amavect
2020-11-22 10:33     ` hiro
2020-11-22 16:57   ` cinap_lenrek
2020-11-22 17:10     ` Amavect
2020-11-24 23:35       ` ori
2020-11-25  0:21         ` Amavect
2020-11-25  9:38           ` hiro
2020-11-25 12:34           ` Ethan Gardener
     [not found]             ` <379baa18-a67f-de65-98b5-d7e08cbb5101@gmail.com>
     [not found]               ` <19260358-767b-4746-a3ff-4ce456a646c5@www.fastmail.com>
     [not found]                 ` <CAFSF3XN_vLb89F=CCzXLkiQvYFFHYm72aSbc1NRkPBtDqwPzFA@mail.gmail.com>
2020-11-29 20:55                   ` Ethan Gardener
2020-11-29 22:15                     ` cinap_lenrek
2020-11-29 22:55                       ` Stuart Morrow
2020-11-29 23:35                         ` cinap_lenrek
2020-11-30  0:10                           ` Stuart Morrow
2020-11-30  0:13                             ` Stuart Morrow
2020-11-30  0:21                             ` Alex Musolino
2020-11-30  1:48                               ` ori
2020-11-30  2:17                                 ` Stanley Lieber [this message]
2020-11-30  9:19                                 ` hiro
2020-11-30 18:26                                 ` Ethan Gardener
2020-11-29 22:26                 ` umbraticus
2020-11-29 22:50                   ` Ethan Gardener
2020-11-22 17:14     ` ori
2020-11-22 20:40   ` hiro
2020-11-22 21:18     ` ori
2020-12-03  2:17     ` magma698hfsp273p9f
2020-11-23 21:16 ` Ethan Gardener
2020-11-23 22:06   ` Amavect
2020-11-23 23:17     ` Ethan Gardener

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=A835C1C4-7340-4D5D-A0F9-F8839C71CB98@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).