From: Marco Wahl <marcowahlsoft@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Marco Wahl <marcowahlsoft@gmail.com>, 36494@debbugs.gnu.org
Subject: bug#36494: 27.0.50; [Proposition] New option to scroll up regardless of eob
Date: Thu, 04 Jul 2019 22:59:11 +0200 [thread overview]
Message-ID: <84ef351ppc.fsf@gmail.com> (raw)
In-Reply-To: <837e8xbw70.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Jul 2019 19:28:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Marco Wahl <marcowahlsoft@gmail.com>
>> Cc: marcowahlsoft@gmail.com, 36494@debbugs.gnu.org
>> Date: Thu, 04 Jul 2019 15:33:38 +0200
>>
>> > How about if we bind S-DOWN and S-UP to commands that scroll to EOB
>> > without introducing any new option? That would mimic pages like Less
>> > which stop at EOB with an unshifted key, but continue scrolling with a
>> > shifted key.
>>
>> That sounds good to me. Also the mimicing of similar features elsewhere.
>
> Would you like to submit a patch along those lines?
Please see the attempt in the attachment.
There is one new function `scroll-lock-next-line-always-scroll' which
gets bound to S-down. Further there are a few tests for this function.
AFAICS the up command needs no special handling with regards to
scroll-lock-mode.
next prev parent reply other threads:[~2019-07-04 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 11:03 bug#36494: 27.0.50; [Proposition] New option to scroll up regardless of eob marcowahlsoft
2019-07-04 13:09 ` Eli Zaretskii
2019-07-04 13:33 ` Marco Wahl
2019-07-04 16:28 ` Eli Zaretskii
2019-07-04 20:59 ` Marco Wahl [this message]
2019-07-04 21:07 ` Marco Wahl
2019-07-13 7:37 ` Eli Zaretskii
2019-07-13 20:10 ` Marco Wahl
2019-07-14 6:25 ` Eli Zaretskii
2019-07-04 20:13 ` Juri Linkov
[not found] <<84ftnmjc37.fsf@gmail.com>
[not found] ` <<83d0iqaqvh.fsf@gnu.org>
2019-07-04 15:50 ` Drew Adams
2019-07-04 18:59 ` Noam Postavsky
2019-07-04 22:28 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84ef351ppc.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=36494@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).