From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 20236@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
"Tory S. Anderson" <torys.anderson@gmail.com>
Subject: bug#20236: 25.0.50; Feature Request: scroll-other-window does not allow setting of scroll function
Date: Sun, 01 May 2022 12:49:57 +0200 [thread overview]
Message-ID: <87zgk1o7ca.fsf@gnus.org> (raw)
In-Reply-To: <87k0gly8q1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 03 Dec 2021 17:05:42 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Hm... perhaps scroll-other-window could look into that other window and
> see whether scroll-{up,down}-command is remapped there, and then use
> that function? Then we wouldn't have to introduce anything new, really.
I've now done this, sort of -- I moved the functions from C to Lisp, and
made them check remapping. But if there aren't any remappings, they
call scroll-up-command instead of scroll-up, which means that other user
options in this area are also heeded.
(I first wondered whether it might make sense to introduce new
scroll-other-window-command indirections here, but that only complicates
things, especially since so many packages remap scroll-other-window.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-01 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 11:09 bug#20236: 25.0.50; Feature Request: scroll-other-window does not allow setting of scroll function Tory S. Anderson
2015-04-02 13:42 ` Stefan Monnier
2021-12-02 10:10 ` Lars Ingebrigtsen
2021-12-02 17:41 ` Juri Linkov
2021-12-03 16:05 ` Lars Ingebrigtsen
2022-05-01 10:49 ` Lars Ingebrigtsen [this message]
2015-04-17 6:05 ` bug#20236: add tiny-change equivalent to 62e7506 Paul Eggert
2015-04-17 6:16 ` bug#20236: 25.0.50; Feature Request: scroll-other-window does not allow setting of scroll function Paul Eggert
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=87zgk1o7ca.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20236@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=torys.anderson@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.