unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandr Vityazev <avityazev@disroot.org>, Po Lu <luangruo@yahoo.com>
Cc: mail@daniel-mendler.de, 69140@debbugs.gnu.org
Subject: bug#69140: 30.0.50; [elpa/vertico] Emacs with vertico-mode freezes if font is too big
Date: Thu, 15 Feb 2024 15:46:40 +0200	[thread overview]
Message-ID: <86bk8hx2kf.fsf@gnu.org> (raw)
In-Reply-To: <87il2qas3z.fsf@disroot.org> (bug-gnu-emacs@gnu.org)

> Cc: mail@daniel-mendler.de
> Date: Thu, 15 Feb 2024 14:23:28 +0300
> From:  Aleksandr Vityazev via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Vertico version 1.7, version 1.3 has also been tested, is incompatible
> with the changes made by the commit -
> caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
> git bisect.
> 
> To reproduce:
> 1. Run emacs -Q
> 2. M-x load-library vertico RET
> 3. M-x vertico-mode RET
> 4. Set a large font, the following is suitable for my 13 inch monitor:
> (set-face-attribute 'default nil :family "monospace" :height 440)
> 5. Call M-x
> Emacs should freeze, sometimes you can unfreeze it with a few presses
> of C-g

Thanks, but why do you think the bug is in Emacs and not in vertico?
The fact that you can unfreeze Emacs with C-g indicates that some Lisp
is involved in what probably is an infloop.  At the very least, could
you please catch a Lisp backtrace when you type C-g, so that we could
see what Lisp is involved?  Also, what exactly does vertico do with
resizing the mini-window, and what should be the value of
resize-mini-windows for reproducing this issue.





  reply	other threads:[~2024-02-15 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 11:23 bug#69140: 30.0.50; [elpa/vertico] Emacs with vertico-mode freezes if font is too big Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-15 13:46 ` Eli Zaretskii [this message]
2024-02-15 14:29   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 16:15     ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 16:38       ` Eli Zaretskii
2024-02-21 17:20         ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 17:47           ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 19:43             ` Eli Zaretskii
2024-02-21 20:22               ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22  6:21                 ` Eli Zaretskii
2024-02-22  6:37                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 10:59                     ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23  2:19                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23 17:12                         ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23 17:59                           ` Eli Zaretskii
2024-02-21 18:56           ` Eli Zaretskii
2024-02-15 17:15   ` Aleksandr Vityazev via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86bk8hx2kf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69140@debbugs.gnu.org \
    --cc=avityazev@disroot.org \
    --cc=luangruo@yahoo.com \
    --cc=mail@daniel-mendler.de \
    /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).