unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: noah <noah.v.peart@gmail.com>, 38502@debbugs.gnu.org
Subject: bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames
Date: Mon, 09 Dec 2019 00:20:01 +0200	[thread overview]
Message-ID: <87sgluxxwu.fsf@mail.linkov.net> (raw)
In-Reply-To: <839c5f10-604a-6d29-dd4f-0128982b6894@gmx.at> (martin rudalics's message of "Sun, 8 Dec 2019 09:58:07 +0100")

tags 38502 fixed
close 38502 27.0.50
quit

>> C-v and M-v should scroll 'minibuffer-selected-window', but
>> C-M-v should scroll the other window from 'minibuffer-selected-window'
>> like it does now.  But maybe this should be configurable?
>>
>> Is there a variable/function with a name like 'minibuffer-selected-other-window'
>> that gives an other window to scroll with C-M-v from the minibuffer or
>> from the window defined by 'minibuffer-selected-window'?
>
> 'other-window-for-scrolling' tries to dynamically find a window that
> shows 'other-window-scroll-buffer'.  So it's the latter we would
> probably have to set.

I see.  So this is fixed now.





  reply	other threads:[~2019-12-08 22:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 19:03 bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames noah
2019-12-05 19:16 ` Eli Zaretskii
2019-12-05 21:59   ` nvp
2019-12-06  0:02 ` Juri Linkov
2019-12-06  1:42   ` nvp
2019-12-08 21:11     ` Juri Linkov
2019-12-08 23:09       ` Drew Adams
2019-12-09 23:39         ` Juri Linkov
2019-12-10  5:07           ` Drew Adams
2019-12-06  7:37   ` martin rudalics
2019-12-06  8:04     ` nvp
2019-12-06  8:36       ` martin rudalics
2019-12-07 23:33     ` Juri Linkov
2019-12-08  8:58       ` martin rudalics
2019-12-08 22:20         ` Juri Linkov [this message]
2019-12-08 23:22           ` nvp
2019-12-08 23:23             ` nvp
2019-12-06  7:48   ` Eli Zaretskii

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=87sgluxxwu.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=38502@debbugs.gnu.org \
    --cc=noah.v.peart@gmail.com \
    --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).