From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 23093@debbugs.gnu.org, nljlistbox2@gmail.com
Subject: bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right
Date: Tue, 22 Mar 2016 21:02:09 +0200 [thread overview]
Message-ID: <838u1a49qm.fsf@gnu.org> (raw)
In-Reply-To: <56F1932A.3060507@gmx.at> (message from martin rudalics on Tue, 22 Mar 2016 19:47:06 +0100)
> Date: Tue, 22 Mar 2016 19:47:06 +0100
> From: martin rudalics <rudalics@gmx.at>
>
> > There seems to have been an (undocumented?) behaviour change -- now when
> > using completion in the minibuffer the frame seems always to be split
> > horizontally (into above-and-below windows) with the completions in the
> > lower window.
> >
> > This change does not seem to me to be an improvement, as now far fewer
> > of the available completions are visible at once.
>
> Customizing ‘temp-buffer-max-height’ would fix that.
>
> > I suppose whether a "portrait" or "landscape" completions window is
> > better probably depends on the number and length of the completions and
> > also on the user's frame size, so presumably the splitting behaviour
> > should be a user option.
>
> It is. Please customize ‘display-buffer-alist’ for the buffer named
> *Completions*.
Hmm... I see neither temp-buffer-resize-mode nor
temp-buffer-max-height are documented in the manual. Would you please
add them (and maybe also discuss how to customize display-buffer-alist
for the *Completions* buffer)? I expect other users to bump into
these issues.
TIA
next prev parent reply other threads:[~2016-03-22 19:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 17:37 bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right N. Jackson
2016-03-22 18:47 ` martin rudalics
2016-03-22 19:02 ` Eli Zaretskii [this message]
2016-03-23 8:09 ` martin rudalics
2016-03-23 15:20 ` Eli Zaretskii
2016-03-23 18:53 ` martin rudalics
2016-03-23 19:43 ` Eli Zaretskii
2016-03-23 20:17 ` N. Jackson
2016-03-24 7:42 ` martin rudalics
2016-03-25 7:42 ` martin rudalics
2016-03-25 8:05 ` Eli Zaretskii
2016-03-25 8:37 ` martin rudalics
2016-03-25 10:39 ` Eli Zaretskii
2020-08-24 18:21 ` Lars Ingebrigtsen
2016-03-22 19:45 ` N. Jackson
2016-03-23 8:09 ` martin rudalics
2016-03-23 21:35 ` Juri Linkov
2016-03-24 7:43 ` martin rudalics
2016-03-24 22:16 ` Juri Linkov
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=838u1a49qm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23093@debbugs.gnu.org \
--cc=nljlistbox2@gmail.com \
--cc=rudalics@gmx.at \
/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.