From: nvp <noah.v.peart@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38502@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames
Date: Thu, 5 Dec 2019 16:59:13 -0500 [thread overview]
Message-ID: <CAPVBTSc0-gn83OekUvFRS9DWqX8g-ED+dMzR9Pw361wv39-iEw@mail.gmail.com> (raw)
In-Reply-To: <83sglyh9az.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
The snazzy new completion coloring is nice though!
On Thu, Dec 5, 2019 at 2:17 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: noah <noah.v.peart@gmail.com>
> > Date: 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
>
> Probably related to recent message/minibuffer-message changes.
>
[-- Attachment #2: Type: text/html, Size: 1196 bytes --]
next prev parent reply other threads:[~2019-12-05 21:59 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPVBTSc0-gn83OekUvFRS9DWqX8g-ED+dMzR9Pw361wv39-iEw@mail.gmail.com \
--to=noah.v.peart@gmail.com \
--cc=38502@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.