From: martin rudalics <rudalics@gmx.at>
To: Leo Liu <sdl.web@gmail.com>, 19355@debbugs.gnu.org
Cc: Juri Linkov <juri@linkov.net>
Subject: bug#19355: 25.0.50; limit the popup window height
Date: Fri, 12 Dec 2014 13:45:32 +0100 [thread overview]
Message-ID: <548AE36C.7060606@gmx.at> (raw)
In-Reply-To: <87vblhtz5m.fsf@gmail.com>
> The popup window from, for example, minibuffer-completion-help, can be
> so tall that the main editing window is squeezed to a few lines
This number of lines is specified by `window-min-height'.
> which
> has the unfortunate side-effect of moving point, pushing some buffer
> text out of the window. This is quite an annoyance. To see this:
>
> 1. Find an elisp file, with the form under edit centred around the
> window.
>
> 2. Try complete for `(s' and assume the window split will be done
> vertically.
We can add the MAX/MIN-HEIGHT/WIDTH arguments of `fit-window-to-buffer'
to the alist entries recognized by `display-buffer'. Then
`minibuffer-completion-help' and friends could set them in a way we'd
have to choose yet. Or we make these globally customizable.
I'm currently rewriting the code for *Completions* windows to make sure
they don't get obscured by an expanding minibuffer window. If you have
a good proposal I can make the necessary changes right away.
martin
next prev parent reply other threads:[~2014-12-12 12:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 1:49 bug#19355: 25.0.50; limit the popup window height Leo Liu
2014-12-12 12:45 ` martin rudalics [this message]
2014-12-12 13:05 ` Leo Liu
2014-12-12 17:19 ` martin rudalics
2014-12-13 0:17 ` Leo Liu
2014-12-13 10:21 ` martin rudalics
2014-12-13 14:41 ` Leo Liu
2014-12-13 20:03 ` martin rudalics
2014-12-14 0:37 ` Leo Liu
2014-12-14 9:03 ` martin rudalics
2014-12-17 0:43 ` Leo Liu
2014-12-17 7:08 ` martin rudalics
2014-12-19 23:10 ` Leo Liu
2014-12-25 10:35 ` martin rudalics
2014-12-25 20:01 ` Juri Linkov
2014-12-26 9:13 ` martin rudalics
2014-12-27 0:57 ` Juri Linkov
2014-12-30 10:15 ` martin rudalics
2014-12-31 0:03 ` Juri Linkov
2014-12-31 18:38 ` martin rudalics
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=548AE36C.7060606@gmx.at \
--to=rudalics@gmx.at \
--cc=19355@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=sdl.web@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).