unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: marcowahlsoft@gmail.com
Cc: 36494@debbugs.gnu.org
Subject: bug#36494: 27.0.50; [Proposition] New option to scroll up regardless of eob
Date: Thu, 04 Jul 2019 16:09:06 +0300	[thread overview]
Message-ID: <83d0iqaqvh.fsf@gnu.org> (raw)
In-Reply-To: <84ftnmjc37.fsf@gmail.com> (marcowahlsoft@gmail.com)

> From: marcowahlsoft@gmail.com
> Date: Thu, 04 Jul 2019 13:03:40 +0200
> 
> Most of the time I find it useful to scroll up in scroll-lock-mode also
> in the case when the end of the buffer is in sight.  With this behavior
> it's possible to scroll up until there is literally (almost) nothing
> left in the buffer.
> 
> This is in opposition to the current behavior of scroll-lock-mode which
> always switches to forward-line if the end of buffer is in sight.
> 
> Find attached a concrete realization.

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.





  reply	other threads:[~2019-07-04 13:09 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 [this message]
2019-07-04 13:33   ` Marco Wahl
2019-07-04 16:28     ` Eli Zaretskii
2019-07-04 20:59       ` Marco Wahl
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=83d0iqaqvh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36494@debbugs.gnu.org \
    --cc=marcowahlsoft@gmail.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.
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).