9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Mon, 27 Jul 2020 16:46:53 -0700	[thread overview]
Message-ID: <A48A911E9EF540C65C90EF28688B83D5@eigenstate.org> (raw)
In-Reply-To: <1CF6DFC0-8085-4A31-A8AB-2F54EE2C8EC6@stanleylieber.com>

> On July 27, 2020 6:06:51 PM EDT, Anthony Martin <ality@pbrane.org> wrote:
>>ori@eigenstate.org once said:
>>> I'm not aware of anything that documents the rather unique ways we
>>> handle scrolling, where how far up the window you are affects how
>>> quick the scrolling goes.
>>
>> From rio(1):
>>
>>  Mousing inside the scroll bar moves text: clicking button 1 with the
>>  mouse pointing inside the scroll bar brings the line at the top of
>>  the win- dow to the cursor's vertical location; button 3 takes the
>>  line at the cursor to the top of the window; button 2, treating the
>>  scroll bar as a ruler, jumps to the indicated portion of the stored
>>  text. Holding a button pressed in the scroll bar will cause the text
>>  to scroll continuously until the button is released.
>>
>>Cheers,
>>  Anthony
> 
> I think ori is talking about scrollwheel behavior, which in any case,
> yes, behaves the same way as clicking inside the scrollbar.

I was -- but I also had forgotten that this was in the rio manpage.

The reason I was thinking of this is because I made triple click
do something useful recently -- and made it work the same across
sam, rio, acme, and vt, and was thinking it'd be nice to have a
single document that described these conventions.



  reply	other threads:[~2020-07-27 23:46 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  9:09 sirjofri+ml-9front
2020-07-27  9:56 ` [9front] " hiro
2020-07-27 15:10 ` Amavect
2020-07-27 15:54   ` Stanley Lieber
2020-07-27 15:58 ` ori
2020-07-27 17:01   ` William Gunnells
2020-07-27 17:29     ` Stanley Lieber
2020-07-27 18:09       ` William Gunnells
2020-07-27 20:01       ` ori
2020-07-27 21:22         ` Ethan Gardener
2020-07-28 19:10           ` cinap_lenrek
2020-07-29 22:36             ` Ethan Gardener
2020-07-27 22:06         ` Anthony Martin
2020-07-27 22:21           ` Stanley Lieber
2020-07-27 23:46             ` ori [this message]
2020-07-27 22:17         ` Stanley Lieber
2020-07-27 22:47           ` Kurt H Maier
2020-07-27 23:50             ` ori
2020-07-28  4:56               ` sirjofri+ml-9front
2020-07-28 10:18                 ` hiro
2020-07-28 11:27                   ` sirjofri+ml-9front
2020-07-28 12:14                     ` hiro
2020-07-28 13:08                       ` sirjofri+ml-9front
2020-07-28 14:16                         ` hiro
2020-07-28 15:01                           ` Stanley Lieber
2020-07-28 15:12                             ` ori
2020-07-28 15:46                               ` Stanley Lieber
2020-07-28 17:25                                 ` hiro
2020-07-28 17:37                                 ` ori
2020-07-28 17:43                                   ` Kurt H Maier
2020-07-28 15:11                         ` ori
2020-07-28 11:29                   ` sirjofri+ml-9front
2020-07-29 17:10                     ` ori
2020-07-30  1:02             ` sl
2020-07-28  9:48           ` hiro
2020-07-30 18:12 ` magma698hfsp273p9f
2020-07-30 18:48   ` kvik
2020-07-30 18:54   ` ori
2020-07-30 19:28     ` Eckard Brauer
2020-07-30 19:59     ` Romano
2020-07-31 13:44       ` kvik
2020-07-31 13:51         ` Stanley Lieber
2020-08-01 15:42         ` Ethan Gardener
2020-07-30 19:15   ` Kurt H Maier
2020-07-31 10:59     ` Ethan Gardener
2020-08-03 18:50       ` magma698hfsp273p9f
2020-08-04 17:13         ` Ethan Gardener
     [not found] <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>
2020-07-30  2:14 ` ori
2020-07-30  3:06   ` Stanley Lieber
2020-07-30  3:12     ` Michael Misch
2020-07-30  8:19       ` hiro
2020-07-30  8:58         ` Kurt H Maier
2020-07-30 12:03       ` 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=A48A911E9EF540C65C90EF28688B83D5@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=sl@stanleylieber.com \
    /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).