From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57823@debbugs.gnu.org
Subject: bug#57823: 29.0.50; image-elide: longer completion causes image to remain too small in buffer
Date: Thu, 15 Sep 2022 22:05:03 +0300 [thread overview]
Message-ID: <YyN3X2v31n2zmL2x@protected.localdomain> (raw)
In-Reply-To: <83mtb1yoio.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-09-15 12:30]:
> > From: Jean Louis <bugs@gnu.support>
> > Date: Thu, 15 Sep 2022 11:35:31 +0300
> >
> >
> > image-elide: longer completion causes image to remain too small in
> > buffer
> >
> > How to reproduce:
> >
> > 1. Dired, open some image;
> >
> > 2. M-x image-TAB TAB to see completions.
> >
> > 3. wait for few seconds, because completion buffer is enlarged image
> > automatically resizes and minimizes itself
> >
> > 4. image-elide asks for the color completion. Same thing, if user reads
> > completions longer than few seconds, the visible image size minimizes
> > automatically.
> >
> > 5. Once function expects user to elide the image, the minimized image
> > does not resize back to fill the frame.
>
> Unless this is specific to image-elide (which I cannot invoke here), I
> cannot reproduce this.
>
> What I tried:
>
> emacs -Q
> C-x C-f etc/images/splash.svg RET
> M-x image- TAB
>
> The image shrinks a bit to fit inside the window.
>
> C-g
>
> The image resizes back to its original size.
Yes, I know it should be that way. Though with image-elide, once the
process starts waiting for key, image remain small.
It is specific.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-09-15 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:35 bug#57823: 29.0.50; image-elide: longer completion causes image to remain too small in buffer Jean Louis
2022-09-15 9:29 ` Eli Zaretskii
2022-09-15 19:05 ` Jean Louis [this message]
2022-09-16 11:18 ` Lars Ingebrigtsen
2022-09-17 2:01 ` Jean Louis
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=YyN3X2v31n2zmL2x@protected.localdomain \
--to=bugs@gnu.support \
--cc=57823@debbugs.gnu.org \
--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).