From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 35592@debbugs.gnu.org
Subject: bug#35592: Use display-buffer-in-direction for completion-like windows
Date: Tue, 21 May 2019 09:32:43 +0200 [thread overview]
Message-ID: <2ab60f7d-764b-3d14-ba6a-c53e712ed71e@gmx.at> (raw)
In-Reply-To: <871s0samni.fsf@mail.linkov.net>
>> The former (it's a three liner). But maybe some work remains wrt
>> action arguments like 'window-min-height', 'window-height' and
>> friends. I doubt that you have already exhausted all possibilities.
>
> Why three-liner? I see one-liners in your comments.
I meant the defun, the doc-string and the body.
> I tried to
> replace the whole display-buffer-below-selected with your one-liner
> (display-buffer-in-direction buffer (cons '(direction . below) alist))
> and also the whole display-buffer-at-bottom with your one-liner
> (display-buffer-in-direction buffer (cons '(direction . bottom) alist))
> and everything works fine, I see no problems.
'display-buffer-in-direction' doesn't yet process 'window-min-height'
(and 'window-min-width') entries correctly. I still have to set up
semantics for these ...
martin
next prev parent reply other threads:[~2019-05-21 7:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 20:40 bug#35592: Use display-buffer-in-direction for completion-like windows Juri Linkov
2019-05-07 8:14 ` martin rudalics
2019-05-07 21:30 ` Juri Linkov
2019-05-08 9:09 ` martin rudalics
2019-05-08 19:32 ` Juri Linkov
2019-05-09 8:12 ` martin rudalics
2019-05-09 19:50 ` Juri Linkov
2019-05-10 5:34 ` Eli Zaretskii
2019-05-11 20:48 ` Juri Linkov
2019-05-12 2:31 ` Eli Zaretskii
2019-05-12 19:17 ` Juri Linkov
2019-05-19 9:17 ` martin rudalics
2019-05-19 19:54 ` Juri Linkov
2019-05-20 8:25 ` martin rudalics
2019-05-20 20:36 ` Juri Linkov
2019-05-21 7:32 ` martin rudalics [this message]
2019-05-21 20:18 ` Juri Linkov
2019-05-22 8:31 ` martin rudalics
2019-06-05 20:57 ` Juri Linkov
2019-05-19 9:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ab60f7d-764b-3d14-ba6a-c53e712ed71e@gmx.at \
--to=rudalics@gmx.at \
--cc=35592@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.