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: 15961@debbugs.gnu.org
Subject: bug#15961: 24.3.50; display-buffer-at-bottom not at bottom
Date: Sun, 24 Nov 2013 11:10:56 +0100	[thread overview]
Message-ID: <5291D0B0.6020109@gmx.at> (raw)
In-Reply-To: <87bo1a3cxo.fsf@mail.jurta.org>

 > In emacs -Q that is wide enough to contain two side-by-side windows
 > in the *scratch* buffer evaluate:
 >
 > (add-to-list 'display-buffer-alist '("\\*Completions\\*" display-buffer-at-bottom (nil)))
 >
 > (display-buffer (get-buffer-create "*Completions*"))
 >
 > The *Completions* window is displayed to the right from the *scratch* window,
 > not below.

Strictly spoken, the new window also appears at the bottom of the frame ;-)

An obvious solution to do what you mean is to bind
`split-width-threshold' to nil in `display-buffer-at-bottom' as

	     (let (split-width-threshold)
	       (setq window (window--try-to-split-window bottom-window alist)))

But this should be better done _around_ calling `display-buffer'.  There
an application should also bind `split-height-threshold' and
`window-min-height' appropriately as well as a specify a `window-height'
alist entry.  Otherwise, Emacs will often refuse to make a new window
which is probably not what we want when displaying *Completions*.

martin





  reply	other threads:[~2013-11-24 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 23:39 bug#15961: 24.3.50; display-buffer-at-bottom not at bottom Juri Linkov
2013-11-24 10:10 ` martin rudalics [this message]
2013-11-24 16:42   ` Stefan Monnier
2013-11-24 17:35     ` martin rudalics
2013-11-25  3:22       ` Stefan Monnier
2013-11-25  7:28         ` martin rudalics
2013-11-25 15:01           ` Stefan Monnier
2013-11-25 16:42             ` martin rudalics
2013-11-28  0:55               ` 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=5291D0B0.6020109@gmx.at \
    --to=rudalics@gmx.at \
    --cc=15961@debbugs.gnu.org \
    --cc=juri@jurta.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 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.