From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
63455@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#63455: 30.0.50; display-buffer-in-direction is always resizing
Date: Mon, 15 May 2023 20:01:49 +0300 [thread overview]
Message-ID: <86ttwdjzpe.fsf@mail.linkov.net> (raw)
In-Reply-To: <8f609c16-2302-2dca-0c5a-b740da6e1686@gmx.at> (martin rudalics's message of "Sat, 13 May 2023 10:56:16 +0200")
> - When the user customizes 'display-buffer-alist' to call another
> display action, say 'display-buffer-below-selected', the window will
> not be resized. Try without and with the first form evaluated:
>
> (setq display-buffer-alist
> '(("*foo*" display-buffer-below-selected)))
>
> (pop-to-buffer (get-buffer-create "*foo*")
> '(display-buffer--maybe-at-bottom))
I tried with your patch, and it works correctly. I guess
this change is for master, not the release branch?
> We could add a buffer-local variable say 'temporary' which the temporary
> buffer functions would set and 'display-buffer' would always obey in
> conjunction with 'temp-buffer-resize-mode'. Then a program or the user
> could set or reset that variable to obtain the desired behavior with
> plain 'display-buffer' calls as well. Whether such an option is clean
> is another question.
Maybe temporary buffers should resize windows by default?
Then such an option should be able to override the default behavior.
next prev parent reply other threads:[~2023-05-15 17:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 1:06 bug#63455: 30.0.50; display-buffer-in-direction is always resizing Michael Heerdegen
2023-05-12 7:39 ` martin rudalics
2023-05-12 17:16 ` Juri Linkov
2023-05-13 8:56 ` martin rudalics
2023-05-15 17:01 ` Juri Linkov [this message]
2023-05-15 18:21 ` Eli Zaretskii
2023-05-16 7:19 ` martin rudalics
2023-05-16 16:35 ` Juri Linkov
2023-05-17 16:56 ` Juri Linkov
2023-05-18 8:29 ` martin rudalics
2023-05-18 15:54 ` Juri Linkov
2023-05-19 7:31 ` martin rudalics
2023-05-19 17:54 ` Juri Linkov
2023-05-20 8:27 ` martin rudalics
2023-05-22 18:03 ` Juri Linkov
2023-05-23 2:30 ` Michael Heerdegen
2023-05-23 18:25 ` Juri Linkov
2023-05-24 2:48 ` Michael Heerdegen
2023-05-12 17:11 ` Juri Linkov
2023-05-13 5:29 ` Michael Heerdegen
2023-05-15 17:02 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ttwdjzpe.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=63455@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=michael_heerdegen@web.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).