From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>, 45945@debbugs.gnu.org
Subject: bug#45945: 28.0.50; Feature request: Some kind of 'max-window-height' parameter for display-buffer-in-direction
Date: Tue, 19 Jan 2021 21:31:43 +0200 [thread overview]
Message-ID: <5b39387e-cce9-1754-f51b-5a72b6de0d5d@yandex.ru> (raw)
In-Reply-To: <87bldlf9zt.fsf@mail.linkov.net>
On 19.01.2021 19:41, Juri Linkov wrote:
>>> It will be helpful to limit the height of the resulting window (either
>>> in lines or in percentages of the parent window height). If the split has
>>> been performed, of course.
>>
>> Looks like I've managed that with 'window-height' alist entry set to
>> a function that wraps fit-window-to-buffer.
>>
>> Commit 4ca808ee7a in master.
>
> Indeed, maybe this could be customizable. For example,
> like there is the customizable variable display-buffer-alist,
> a new customizable variable with a name like post-display-buffer-functions
> could be used to add/remove such hooks as fit-window-to-buffer.
> like temp-buffer-resize-mode does. But this should a more general feature.
The general feature sounds interesting, but I personally have avoided
customizing even display-buffer-alist so far, and doing that with either
of the variables (the existing or the proposed one) seems pretty far
from the capabilities of an average Emacs user.
Speaking of customization, I rather wondered whether the max height
percentage in xref-show-definitions-buffer-at-bottom should be
customizable (as a float number, probably).
prev parent reply other threads:[~2021-01-19 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 1:55 bug#45945: 28.0.50; Feature request: Some kind of 'max-window-height' parameter for display-buffer-in-direction Dmitry Gutov
2021-01-19 1:11 ` Dmitry Gutov
2021-01-19 17:41 ` Juri Linkov
2021-01-19 19:31 ` Dmitry Gutov [this message]
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=5b39387e-cce9-1754-f51b-5a72b6de0d5d@yandex.ru \
--to=dgutov@yandex.ru \
--cc=45945@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.