From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Al Petrofsky <al@petrofsky.org>, 64139@debbugs.gnu.org
Subject: bug#64139: 28.2; Scrolling problems in miniwindow
Date: Mon, 19 Jun 2023 20:20:30 +0300 [thread overview]
Message-ID: <86r0q7sjea.fsf@mail.linkov.net> (raw)
In-Reply-To: <83edm9p7qm.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Jun 2023 10:09:05 +0300")
> M-v in the minibuffer is bound to switch-to-completions, so I'm unsure
> what you expected here.
>
> Adding Juri who worked on the scrolling commands in the minibuffer.
I worked only on the <down> key bound to next-line-or-history-element.
prev parent reply other threads:[~2023-06-19 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 0:26 bug#64139: 28.2; Scrolling problems in miniwindow Al Petrofsky
2023-06-18 7:09 ` Eli Zaretskii
2023-06-18 9:07 ` Al Petrofsky
2023-06-19 22:33 ` Al Petrofsky
2023-06-21 15:01 ` Eli Zaretskii
2023-06-19 17:20 ` Juri Linkov [this message]
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=86r0q7sjea.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=64139@debbugs.gnu.org \
--cc=al@petrofsky.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).