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: Wed, 12 Jan 2022 21:45:00 +0200	[thread overview]
Message-ID: <86y23kpwlf.fsf@mail.linkov.net> (raw)
In-Reply-To: <8335ls69cy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Jan 2022 21:29:33 +0200")

>> >> There are also nice commands: M-<home> (beginning-of-buffer-other-window)
>> >> and M-<end> (end-of-buffer-other-window), but for no reason they recenter
>> >> the other window after moving to the beginning/end.
>> >> 
>> >> It would be better to remove this disservice:
>> >
>> > This is age-old behavior.  Why change it because you happen to dislike
>> > it?
>> 
>> The problem is that with its current implementation, it's unusable:
>> when the window height is 75 lines, then typing M-<end> leaves
>> half-screen empty.
>
> If you start typing at the end of the buffer, the half-empty window
> will immediately make sense.

You can't start typing because it's in another window.

> Are you using scroll-conservatively, perhaps?  If so, I can understand
> why you don't like this behavior.  But that's your subjective opinion,
> and I see no reason to change this by default.

This problem is reproducible in emacs -Q:
visit e.g. TODO with 'C-h C-t', split windows with 'C-x 3',
and type 'M-<end>'.  Then another window is recentered.

>> But fortunately this can be fixed since Emacs 28 introduced a new key
>> C-M-S-l to recenter the other window, so it's now easy to type it
>> when the user needs to recenter the other window.
>
> Great.

So everyone who wants to recenter, can type: 'M-<end> M-C-S-l'.





  reply	other threads:[~2022-01-12 19:45 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 [this message]
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=86y23kpwlf.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).