From: martin rudalics <rudalics@gmx.at>
To: Clemens <clemens.radermacher@posteo.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 44080@debbugs.gnu.org
Subject: bug#44080: 27.1; Display behavior of overlays `after-string` in resizable minibuffer frames
Date: Wed, 21 Oct 2020 15:49:00 +0200 [thread overview]
Message-ID: <82e8f1b4-c3cb-6aec-45d3-e413da4a1b58@gmx.at> (raw)
In-Reply-To: <10267321-400d-5d36-1558-070a24476a03@posteo.de>
> The version above invokes infinite recursion so I would rather recommend
> something like the following for affected users ...
IMO advices are much too complicated to handle this issue. I'd proceed
in the traditional way:
(1) Rename 'fit-frame-to-buffer' to say 'fit-frame-to-buffer-1' and give
that function two new arguments FROM and TO. In its
'window-text-pixel-size' call, replace the "t t" with "from to".
(2) Provide a new function 'fit-frame-to-buffer' with the same singature
as the old 'fit-frame-to-buffer' that calls `fit-frame-to-buffer-1' with
FROM and TO t.
(3) Provide a new function 'fit-mini-frame-to-buffer' that calls
'fit-frame-to-buffer-1' with FROM and TO nil. Offer that function as
first choice when customizing 'resize-mini-frames' and call it in
'window--resize-mini-frame' when 'resize-mini-frames' is nil.
If 'fit-frame-to-buffer' has additional defects when used for resizing
mini frames, we could try to fix them in 'fit-mini-frame-to-buffer' as
well. WDYT?
martin
next prev parent reply other threads:[~2020-10-21 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 18:39 bug#44080: 27.1; Display behavior of overlays `after-string` in resizable minibuffer frames Clemens
2020-10-19 19:43 ` Eli Zaretskii
2020-10-20 7:21 ` martin rudalics
2020-10-20 9:27 ` Clemens
2020-10-20 14:40 ` martin rudalics
2020-10-20 15:19 ` Clemens
2020-10-20 17:02 ` Clemens
2020-10-21 9:11 ` Clemens
2020-10-21 13:49 ` martin rudalics [this message]
2020-10-21 14:13 ` Clemens
2020-10-21 16:05 ` martin rudalics
2020-10-21 17:20 ` Clemens
2020-10-21 17:25 ` martin rudalics
2020-10-22 12:39 ` Clemens
2020-10-22 16:26 ` martin rudalics
2020-10-24 13:08 ` Clemens
2020-10-24 13:39 ` Robert Pluim
2020-10-27 18:15 ` Clemens
2020-10-26 18:24 ` martin rudalics
2020-10-26 18:32 ` Eli Zaretskii
2020-10-26 20:53 ` Clemens
2020-10-27 9:08 ` martin rudalics
2020-10-27 12:10 ` Clemens
2020-10-27 18:02 ` martin rudalics
2020-10-27 18:29 ` Clemens
2020-10-21 19:45 ` Andrii Kolomoiets
2020-10-21 15:00 ` Eli Zaretskii
2020-10-27 18:23 ` bug#44080: Fixed for Emacs 27.2 Clemens
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=82e8f1b4-c3cb-6aec-45d3-e413da4a1b58@gmx.at \
--to=rudalics@gmx.at \
--cc=44080@debbugs.gnu.org \
--cc=clemens.radermacher@posteo.de \
--cc=eliz@gnu.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 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).