From: Eli Zaretskii <eliz@gnu.org>
To: Clemens <clemens.radermacher@posteo.de>,
martin rudalics <rudalics@gmx.at>
Cc: 44080@debbugs.gnu.org
Subject: bug#44080: 27.1; Display behavior of overlays `after-string` in resizable minibuffer frames
Date: Mon, 19 Oct 2020 22:43:41 +0300 [thread overview]
Message-ID: <83v9f6ngr6.fsf@gnu.org> (raw)
In-Reply-To: <db602698-c755-2b48-ae4e-4f3ef80821c3@posteo.de> (message from Clemens on Mon, 19 Oct 2020 20:39:15 +0200)
> From: Clemens <clemens.radermacher@posteo.de>
> Date: Mon, 19 Oct 2020 20:39:15 +0200
>
> 1. `emacs -Q --eval "(setq default-frame-alist '((minibuffer . nil)))"`
> 2. `eval-buffer` with following code:
>
> ```elisp
> (setq resize-mini-frames t)
>
> (defvar ov (make-overlay (point-min) (point-min) nil t t))
>
> (minibuffer-with-setup-hook
> (lambda ()
> (move-overlay ov
> (point-max)
> (point-max)
> (current-buffer))
> ;; Note the initial newline...
> (overlay-put ov 'after-string "\nHey there, I'm hidden initially
> and will hide again after any space in the input"))
> (read-string "Hi? "))
> ```
>
> 3. Start typing
>
> As stated in the after-string text, it is initially hidden, shows when
> you input some text and gets hidden again every time you type a space.
It looks like the problem is in fit-frame-to-buffer: it is not
prepared to handle after-string at the end of the prompt.
Specifically, the fact that the 2nd and the 3rd args of the call to
window-text-pixel-size are both t causes the function to return the
value which doesn't account for the after-string.
next prev parent reply other threads:[~2020-10-19 19:43 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 [this message]
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
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=83v9f6ngr6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44080@debbugs.gnu.org \
--cc=clemens.radermacher@posteo.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).