unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51210@debbugs.gnu.org
Subject: bug#51210: Customizable other-window-for-scrolling
Date: Thu, 27 Jan 2022 19:40:51 +0200	[thread overview]
Message-ID: <86tudp6pr0.fsf@mail.linkov.net> (raw)
In-Reply-To: <8335lckj1b.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jan 2022 21:53:04 +0200")

>> (defun beginning-of-buffer-other-window (arg)
>>   (with-selected-window (other-window-for-scrolling)
>>     ;; Set point and mark in that window's buffer.
>>     (with-no-warnings
>>       (beginning-of-buffer arg))
>>     ;; Set point accordingly.
>>     (recenter '(t))))
>> 
>> It's not clear what does the last comment mean.
>> 'recenter' should set point accordingly to what?
>> And what does (recenter '(t)) do at the beginning of the buffer?
>
> It isn't beginning of buffer, it's where (beginning-of-buffer arg)
> puts point when ARG is non-nil.  See the doc string of
> beginning-of-buffer.

Sorry, I didn't notice it takes an argument.  Then it's strange
that it doesnt't recenter according to recenter-top-bottom that
uses recenter-positions.  So two most useful behaviors
(recenter-top-bottom for beginning-of-buffer-other-window and
no recentering for end-of-buffer-other-window) are not supported.
Since the default can't be changed, maybe a new optional argument
could define whether to use recenter-top-bottom, or no recenter at all.





  reply	other threads:[~2022-01-27 17:40 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
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 [this message]
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=86tudp6pr0.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=51210@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).