From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 51210@debbugs.gnu.org
Subject: bug#51210: Customizable other-window-for-scrolling
Date: Tue, 04 Jan 2022 10:38:41 +0200 [thread overview]
Message-ID: <86o84revzi.fsf@mail.linkov.net> (raw)
In-Reply-To: <96d50c26-ea56-5ff6-3cc3-25652d744ca4@gmx.at> (martin rudalics's message of "Fri, 31 Dec 2021 10:11:53 +0100")
>>> Maybe a variable 'other-window-scroll-window' whose value could be a
>>> function to get that window.
>>
>> Since there is already the word "window" in the function name,
>> maybe better would be 'other-window-scroll-default' that hints
>> that it overrides the default that is the next window:
>
> Since we already have 'other-window-scroll-buffer' this might be
> confusing.
It's named intentionally to be similar with 'other-window-scroll-buffer'.
> And shouldn't a window, if specified, override a specified buffer?
Its purpose is to override only the part that hard-codes 'next-window'.
> BTW I think we should move 'other-window-for-scrolling' to
> window.el - all it does is call Lisp primitives. And turn
> scroll_command into 'Fscroll_command' (or, better 'Fscroll_window') so
> things like 'scroll-down' (or, better 'scroll-window-down') and
> 'scroll-other-window-down' could end up in window.el too. But maybe I'm
> missing some important detail.
I agree it would be nice to move scrolling commands to Lisp.
next prev parent reply other threads:[~2022-01-04 8:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 17:19 bug#51210: Customizable other-window-for-scrolling Juri Linkov
2021-10-14 17:31 ` Eli Zaretskii
2021-10-14 17:58 ` Juri Linkov
2021-10-14 18:06 ` Eli Zaretskii
2021-10-14 18:25 ` Juri Linkov
2021-10-14 18:37 ` Eli Zaretskii
2021-10-14 18:45 ` Juri Linkov
2021-10-14 18:52 ` Eli Zaretskii
2021-10-14 17:37 ` jakanakaevangeli
2021-10-14 17:59 ` Juri Linkov
2021-10-14 18:04 ` Eli Zaretskii
2021-10-14 17:47 ` martin rudalics
2021-10-14 18:00 ` Juri Linkov
2021-12-29 17:31 ` Juri Linkov
2021-12-31 9:11 ` martin rudalics
2022-01-04 8:38 ` Juri Linkov [this message]
2022-01-04 10:27 ` martin rudalics
2022-01-04 17:37 ` Juri Linkov
2022-01-11 17:29 ` Juri Linkov
2022-01-11 18:40 ` Juri Linkov
2022-01-11 18:58 ` Juri Linkov
2022-01-11 20:08 ` Eli Zaretskii
2022-01-12 18:04 ` Juri Linkov
2022-01-12 19:29 ` Eli Zaretskii
2022-01-12 19:45 ` Juri Linkov
2022-01-12 19:51 ` Eli Zaretskii
2022-01-12 19:59 ` Juri Linkov
2022-01-12 20:41 ` Eli Zaretskii
2022-01-17 8:44 ` Juri Linkov
2022-01-17 12:33 ` Eli Zaretskii
2022-01-24 19:42 ` Juri Linkov
2022-01-24 19:53 ` Eli Zaretskii
2022-01-27 17:40 ` Juri Linkov
2022-01-28 13:45 ` Eli Zaretskii
2022-01-29 18:53 ` Juri Linkov
2022-01-04 13:13 ` Eli Zaretskii
2022-01-04 17:40 ` Juri Linkov
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=86o84revzi.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=51210@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).