From: martin rudalics <rudalics@gmx.at>
To: "Dmitry Gutov" <dgutov@yandex.ru>,
"Daniel Martín" <mardani29@yahoo.es>,
45581-done@debbugs.gnu.org
Subject: bug#45581: 28.0.50; C-M-v in xref buffers shows a different buffer when scrolling
Date: Sun, 3 Jan 2021 09:40:13 +0100 [thread overview]
Message-ID: <d43cfd4b-e9c9-85ed-56aa-8e73efc14a9f@gmx.at> (raw)
In-Reply-To: <bd8c2ec0-0c9f-b13b-79cb-aad90202e7b4@yandex.ru>
> As a result, C-M-v doesn't always scroll the "target location" window anymore (at least, not when there are at least 3 windows on the frame).
>
> I wonder if we can/should do something about it. Other standard commands don't seem to worry about that, though.
I doubt that anybody cares. My suggestion back then was just bad.
'other-window-scroll-buffer' is an ill-advised concept which can fly
only if the buffer where it is set locally is small (so a user will not
wonder about what that buffer has been conceived for and, for example,
ask questions about its modes or keymaps) is displayed for a short time
only and the visibility of the buffer it refers to is absolutely crucial
for the current workflow. Neither of these conditions is given in the
present context and I doubt that they are given in any of the other
occurrences of that variable.
martin
next prev parent reply other threads:[~2021-01-03 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m135zlzj0l.fsf.ref@yahoo.es>
2020-12-31 22:51 ` bug#45581: 28.0.50; C-M-v in xref buffers shows a different buffer when scrolling Unknown
2021-01-01 22:43 ` Dmitry Gutov
2021-01-02 8:25 ` martin rudalics
2021-01-02 18:58 ` Dmitry Gutov
2021-01-03 8:40 ` martin rudalics [this message]
2021-01-04 0:22 ` Dmitry Gutov
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=d43cfd4b-e9c9-85ed-56aa-8e73efc14a9f@gmx.at \
--to=rudalics@gmx.at \
--cc=45581-done@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mardani29@yahoo.es \
/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).