From: martin rudalics <rudalics@gmx.at>
To: nvp <noah.v.peart@gmail.com>
Cc: 38502@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#38502: 27.0.50; minibuffer-scroll-other-window with multiple frames
Date: Fri, 6 Dec 2019 09:36:21 +0100 [thread overview]
Message-ID: <a5d7c069-b750-3b4d-cf71-c839d6987b96@gmx.at> (raw)
In-Reply-To: <CAPVBTSdKz+F3VpEYHB-oxP_qjtB_RZkDzqz_PaU_13=0O40+Tg@mail.gmail.com>
> I've noticed that the new completion windows can also become
> much larger than they used to be, eg. covering nearly everything
> completing after "(ma" for example. I'm sure this is customizable,
> but is there a general consensus on what/which real estate they
> should take up?
Are you sure this has changed "recently"? If you have
'temp-buffer-resize-mode' enabled, the maximum height is specified by
the option 'temp-buffer-max-height'. With 'temp-buffer-resize-mode'
disabled there is no such bound but I see no recent change in behavior
either.
> I think leaving decent portions of the calling buffers can be quite
> useful at times in order to "think as little as possible", eg.
> avoid needing to check back to finish a though.
Try with 'temp-buffer-resize-mode' enabled. If you think that the
customization used there helps, we could try to implement something
similar when that mode is not enabled.
martin
next prev parent reply other threads:[~2019-12-06 8:36 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 [this message]
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=a5d7c069-b750-3b4d-cf71-c839d6987b96@gmx.at \
--to=rudalics@gmx.at \
--cc=38502@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).