unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: noah <noah.v.peart@gmail.com>
Cc: 38502@debbugs.gnu.org
Subject: bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames
Date: Fri, 06 Dec 2019 02:02:53 +0200	[thread overview]
Message-ID: <875zius4lu.fsf@mail.linkov.net> (raw)
In-Reply-To: <874kyezjbd.fsf@gmail.com> (noah's message of "Thu, 05 Dec 2019 14:03:18 -0500")

> I think this is new within the last week or so.
> When a completion frame pops up while using the minibuffer,
> normally the minibuffer-scroll-other-window(-down) functions
> scroll the completion window.  However, now when emacs is split
> into two horizontal frames, these functions ignore the
> completion buffer and scroll the others.
>
> To reproduce from emacs -Q:
>
>     C-x 3
>     M-: (mak
>     TAB for completions
>     C-M-v

TAB and S-TAB should scroll the the completion buffer.  But what about C-M-v?
Is it documented somewhere what buffer it's intended to scroll?
I can find only this text in (info "(emacs) Minibuffer Edit"):

     The ‘C-M-v’ command in the minibuffer scrolls the help text from
  commands that display help text of any sort in another window.  You can
  also scroll the help text with ‘M-<PageUp>’ and ‘M-<PageDown>’ (or,
  equivalently, ‘M-<prior>’ and ‘M-<next>’).  This is especially useful
  with long lists of possible completions.

Does this mean the help text is the same as the completion buffer?

If yes, then this patch should fix it:

diff --git a/lisp/simple.el b/lisp/simple.el
index 47ce0364d1..7d91678ff7 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -1517,6 +1517,7 @@ read-expression-map
     ;; Might as well bind TAB to completion, since inserting a TAB char is
     ;; much too rarely useful.
     (define-key m "\t" 'completion-at-point)
+    (define-key m [remap minibuffer-scroll-other-window] 'scroll-other-window)
     (set-keymap-parent m minibuffer-local-map)
     m))
 






  parent reply	other threads:[~2019-12-06  0:02 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 [this message]
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
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=875zius4lu.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=38502@debbugs.gnu.org \
    --cc=noah.v.peart@gmail.com \
    /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).