all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 23093@debbugs.gnu.org, "N. Jackson" <nljlistbox2@gmail.com>
Subject: bug#23093: 25.0.92; Change for the worse: minibuffer completion window splits below rather that right
Date: Thu, 24 Mar 2016 08:43:36 +0100	[thread overview]
Message-ID: <56F39AA8.3030401@gmx.at> (raw)
In-Reply-To: <87mvpoub9o.fsf@mail.linkov.net>

 > Before adding a new defcustom variable, could we try to make the
 > behavior more DWIM and automatically detect a window configuration
 > where displaying *Completions* side-by-side makes more sense like
 > in frames with 48-characters height and 2*80-characters width.

IIUC the current scheme pretty well handles the case where multiple
windows are already present when completion is attempted.  And IIRC we
also wanted the *Completions* window appear near the echo area.  Doing
both of these for side-by-side windows seems pretty contrived.  I think
that describing an alternative ‘display-buffer-alist’ spec in the manual
should be sufficient.

 > Is it possible to tune ‘temp-buffer-max-height’ to handle this?

‘temp-buffer-max-height’ is effective only if ‘temp-buffer-resize-mode’
is enabled.  ‘temp-buffer-resize-mode’ is not enabled by default.

 > Or maybe we need to add new conditional actions like
 > ‘display-buffer-below-selected-if-high-enough’ or
 > ‘display-buffer-in-right-window-if-height-is-narrow’ or?

Rather not.  In some sense we do the former already although IIUC we
never consult the number of completions before splitting off the window.
The latter looks like a special form of ‘split-window-sensibly’ with all
its problems.

martin






  reply	other threads:[~2016-03-24  7:43 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
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 [this message]
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=56F39AA8.3030401@gmx.at \
    --to=rudalics@gmx.at \
    --cc=23093@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=nljlistbox2@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 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.