From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45688@debbugs.gnu.org
Subject: bug#45688: 28.0.50; New action for display-buffer?
Date: Mon, 04 Oct 2021 20:31:00 +0300 [thread overview]
Message-ID: <87bl44d98r.fsf@mail.linkov.net> (raw)
In-Reply-To: <3ab5fd34-ac8f-86cd-f0b7-5cfdf7befa40@gmx.at> (martin rudalics's message of "Mon, 4 Oct 2021 10:28:18 +0200")
>>>> Indeed, better would be to add an option to not resize it by describe-function.
>>>> Maybe by adding a new option 'after-display-buffer-function' and set it
>>>> by default to 'shrink-window-if-larger-than-buffer' in *Help* buffers?
>>>
>>> You can already use a 'window-height' alist entry and set it to
>>> 'shrink-window-if-larger-than-buffer'. What would an
>>> 'after-display-buffer-function' option do differently?
>>
>> It seems the patch that you recently sent to emacs-devel fixes this problem?
>
> You mean this problem
>
> The problem is that currently shrink-window-if-larger-than-buffer
> is used in many commands by default, but this behavior is hard-coded
> and can't be disabled by customization. These commands include
> help commands, vc-log, vc-diff, ...
>
> supposedly caused by 'temp-buffer-resize-mode'?
Your recent patch in emacs-devel allows customization of help commands,
but not vc-log, vc-diff. A separate request could be created for
customization of shrink-window-if-larger-than-buffer in vc-log, vc-diff.
(I mistakenly assumed that help-mode uses shrink-window-if-larger-than-buffer,
but actually help-mode resizes with 'temp-buffer-resize-mode').
> Would we then be able to close this bug or is there anything else left?
I don't know, Lars opened this request. And I reported this problem
only after you mentioned 'temp-buffer-resize-mode'.
next prev parent reply other threads:[~2021-10-04 17:31 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 12:02 bug#45688: 28.0.50; New action for display-buffer? Lars Ingebrigtsen
2021-01-06 13:36 ` martin rudalics
2021-01-06 14:09 ` Lars Ingebrigtsen
2021-01-06 15:52 ` martin rudalics
2021-01-07 11:45 ` Lars Ingebrigtsen
2021-01-07 13:18 ` martin rudalics
2021-01-07 14:47 ` Lars Ingebrigtsen
2021-01-07 15:17 ` martin rudalics
2021-01-07 15:35 ` martin rudalics
2021-01-07 15:49 ` Lars Ingebrigtsen
2021-01-07 16:54 ` martin rudalics
2021-01-06 15:45 ` Eli Zaretskii
2021-01-06 17:20 ` Lars Ingebrigtsen
2021-01-06 18:17 ` Eli Zaretskii
2021-01-07 11:40 ` Lars Ingebrigtsen
2021-01-07 13:17 ` martin rudalics
2021-01-07 15:39 ` Lars Ingebrigtsen
2021-01-07 16:54 ` martin rudalics
2021-01-10 11:24 ` Lars Ingebrigtsen
2021-01-10 16:05 ` martin rudalics
2021-01-10 16:14 ` martin rudalics
2021-01-11 14:43 ` Lars Ingebrigtsen
2021-01-11 18:23 ` martin rudalics
2021-01-11 18:55 ` martin rudalics
2021-01-19 3:20 ` Lars Ingebrigtsen
2021-01-11 19:05 ` Lars Ingebrigtsen
2021-01-12 9:06 ` martin rudalics
2021-01-19 3:26 ` Lars Ingebrigtsen
2021-01-20 8:08 ` martin rudalics
2021-01-20 16:34 ` Lars Ingebrigtsen
2021-01-20 17:11 ` martin rudalics
2021-01-19 17:50 ` Juri Linkov
2021-01-20 8:09 ` martin rudalics
2021-01-20 21:45 ` Juri Linkov
2021-01-25 19:03 ` martin rudalics
2021-01-25 20:08 ` Juri Linkov
2021-01-26 15:57 ` martin rudalics
2021-01-27 9:38 ` Juri Linkov
2021-01-28 9:40 ` martin rudalics
2021-10-03 18:12 ` Juri Linkov
2021-10-04 8:28 ` martin rudalics
2021-10-04 17:31 ` Juri Linkov [this message]
2021-10-05 6:43 ` Lars Ingebrigtsen
2021-10-05 8:10 ` martin rudalics
2021-10-05 16:49 ` Juri Linkov
2021-10-06 7:41 ` martin rudalics
2021-10-06 17:45 ` Juri Linkov
2021-10-13 8:36 ` martin rudalics
2021-01-11 14:45 ` Lars Ingebrigtsen
2021-01-07 18:43 ` Juri Linkov
2021-01-08 8:31 ` martin rudalics
2021-01-10 11:26 ` Lars Ingebrigtsen
2021-01-12 18:36 ` Juri Linkov
2021-01-19 17:52 ` Juri Linkov
2021-01-25 20:10 ` Juri Linkov
2021-01-26 15:57 ` martin rudalics
2021-01-27 9:35 ` Juri Linkov
2021-01-28 9:40 ` martin rudalics
2021-01-28 18:46 ` Juri Linkov
2021-01-29 7:51 ` martin rudalics
2021-01-06 17:41 ` Juri Linkov
2021-01-06 18:28 ` Drew Adams
2021-01-06 18:47 ` 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
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=87bl44d98r.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=45688@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).