unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aleksandr Vityazev via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 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: Wed, 21 Feb 2024 20:20:14 +0300	[thread overview]
Message-ID: <87zfvt3fap.fsf@disroot.org> (raw)
In-Reply-To: <86jzmxn579.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Feb 2024 18:38:02 +0200")

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

On 2024-02-21 18:38, Eli Zaretskii wrote:

>> From: Aleksandr Vityazev <avityazev@disroot.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  69140@debbugs.gnu.org,
>>   mail@daniel-mendler.de
>> Date: Wed, 21 Feb 2024 19:15:57 +0300
>> 
>> 3. M-x test-dispatch
>> 4. Try playing with the parameters test1, test2, test3, test4. At the
>> same time you can put Emacs into full screen mode and back into windowed
>> mode, where it will occupy half of the screen. Initially, calling the
>> parameters test1, test2, test3, test4 in the transient window will be
>> delayed and everything can be canceled with C-g, after a few repetitions
>> Emacs hangs completely.
>
> Thanks, but I don't understand what to do after "m-x test-dispatch".
> Please tell in more details what you mean in Step 4, in terms of what
> I need to type after "M-x test-dispatch".  (I tried several things,
> but couldn't get any interesting effects, let alone a hang.)

I run test-dispatch, for example I press "r", which calls the
minibuffer. At this point, Emacs is already starting to freeze for me; if
I change the full-screen to windowed mode several times, everything gets
worse.  If nothing happens after pressing "r" you can try other bound
letters.

In fact, I can call commands through the tool-bar or menu-bar, but
everything that is displayed in the window or minibuffer does not
change. Was able to switch to the *Bactrace* buffer and save it via the
menu bar.

Bactrace is attached.

[-- Attachment #2: bactrace --]
[-- Type: text/plain, Size: 6809 bytes --]

Debugger entered--Lisp error: (quit)
  apply(debug (error (quit)))
  transient--exit-and-debug(error (quit))
  redisplay_internal\ \(C\ function\)()
  read-from-minibuffer("Test2: " nil (keymap (remap keymap (minibuffer-completion-help . crm-completion-help) (minibuffer-complete-word . crm-complete-word) (minibuffer-complete . crm-complete)) keymap (menu-bar keymap (minibuf "Minibuf" keymap (tab menu-item "Complete" minibuffer-complete :help "Complete as far as possible") (space menu-item "Complete Word" minibuffer-complete-word :help "Complete at most one word") (63 menu-item "List Completions" minibuffer-completion-help :help "Display all possible completions") "Minibuf")) (M-down . minibuffer-next-completion) (M-up . minibuffer-previous-completion) (27 keymap (13 . minibuffer-choose-completion) (103 keymap (27 keymap (99 . switch-to-completions))) (118 . switch-to-completions)) (prior . switch-to-completions) (63 . minibuffer-completion-help) (32 . minibuffer-complete-word) (backtab . minibuffer-complete) (9 . minibuffer-complete) keymap (menu-bar keymap (minibuf "Minibuf" keymap (previous menu-item "Previous History Item" previous-history-element :help "Put previous minibuffer history element in the minibuffer") (next menu-item "Next History Item" next-history-element :help "Put next minibuffer history element in the minibuffer") (isearch-backward menu-item "Isearch History Backward" isearch-backward :help "Incrementally search minibuffer history backward") (isearch-forward menu-item "Isearch History Forward" isearch-forward :help "Incrementally search minibuffer history forward") (return menu-item "Enter" exit-minibuffer :key-sequence "\15" :help "Terminate input and exit minibuffer") (quit menu-item "Quit" abort-recursive-edit :help "Abort input and exit minibuffer") "Minibuf")) (24 keymap (down . minibuffer-complete-defaults) (up . minibuffer-complete-history)) (13 . exit-minibuffer) (10 . exit-minibuffer) (7 . abort-minibuffers) (C-tab . file-cache-minibuffer-complete) (9 . self-insert-command) (XF86Back . previous-history-element) (up . previous-line-or-history-element) (prior . previous-history-element) (XF86Forward . next-history-element) (down . next-line-or-history-element) (next . next-history-element) (27 keymap (60 . minibuffer-beginning-of-buffer) (114 . previous-matching-history-element) (115 . next-matching-history-element) (112 . previous-history-element) (110 . next-history-element))) nil nil nil nil)
  completing-read-multiple("Test2: " ("nonsdlslde" "slsdl" "2323" "ldslld" "30203" "llx" "ldslsd"))
  (lambda (prompt _initial-input _history) (completing-read-multiple prompt '("nonsdlslde" "slsdl" "2323" "ldslld" "30203" "llx" "ldslsd")))("Test2: " nil transient--history)
  #f(compiled-function (obj) "Read a value while taking care of history.\n\nThis method is suitable for a wide variety of infix commands,\nincluding but not limited to inline arguments and variables.\n\nIf you do not use this method for your own infix class, then\nyou should likely replicate a lot of the behavior of this\nmethod.  If you fail to do so, then users might not appreciate\nthe lack of history, for example.\n\nOnly for very simple classes that toggle or cycle through a very\nlimited number of possible values should you replace this with a\nsimple method that does not handle history.  (E.g., for a command\nline switch the only possible values are \"use it\" and \"don't use\nit\", in which case it is pointless to preserve history.)" #<bytecode 0x1d0443cdbe7f1dda>)(#<test-transient-multi test-transient-multi-47e882>)
  apply(#f(compiled-function (obj) "Read a value while taking care of history.\n\nThis method is suitable for a wide variety of infix commands,\nincluding but not limited to inline arguments and variables.\n\nIf you do not use this method for your own infix class, then\nyou should likely replicate a lot of the behavior of this\nmethod.  If you fail to do so, then users might not appreciate\nthe lack of history, for example.\n\nOnly for very simple classes that toggle or cycle through a very\nlimited number of possible values should you replace this with a\nsimple method that does not handle history.  (E.g., for a command\nline switch the only possible values are \"use it\" and \"don't use\nit\", in which case it is pointless to preserve history.)" #<bytecode 0x1d0443cdbe7f1dda>) #<test-transient-multi test-transient-multi-47e882>)
  #f(compiled-function (&rest args) #<bytecode 0xe3ded132d7c1c5e>)(#<test-transient-multi test-transient-multi-47e882>)
  #f(compiled-function (cl--cnm obj) #<bytecode -0xa6f70d64c5256f0>)(#f(compiled-function (&rest args) #<bytecode 0xe3ded132d7c1c5e>) #<test-transient-multi test-transient-multi-47e882>)
  apply(#f(compiled-function (cl--cnm obj) #<bytecode -0xa6f70d64c5256f0>) #f(compiled-function (&rest args) #<bytecode 0xe3ded132d7c1c5e>) #<test-transient-multi test-transient-multi-47e882>)
  #f(compiled-function (obj) "Refresh the transient buffer buffer calling the next method.\n\nAlso wrap `cl-call-next-method' with two macros:\n- `transient--with-suspended-override' allows use of minibuffer.\n- `transient--with-emergency-exit' arranges for the transient to\n  be exited in case of an error." #<bytecode -0x9d330106cd54cf8>)(#<test-transient-multi test-transient-multi-47e882>)
  apply(#f(compiled-function (obj) "Refresh the transient buffer buffer calling the next method.\n\nAlso wrap `cl-call-next-method' with two macros:\n- `transient--with-suspended-override' allows use of minibuffer.\n- `transient--with-emergency-exit' arranges for the transient to\n  be exited in case of an error." #<bytecode -0x9d330106cd54cf8>) #<test-transient-multi test-transient-multi-47e882> nil)
  transient-infix-read(#<test-transient-multi test-transient-multi-47e882>)
  transient--default-infix-command()
  apply(transient--default-infix-command nil)
  #f(compiled-function (fn &rest args) (interactive nil) #<bytecode 0x1599241be4a7ac75>)(transient--default-infix-command)
  funcall-interactively(#f(compiled-function (fn &rest args) (interactive nil) #<bytecode 0x1599241be4a7ac75>) transient--default-infix-command)
  apply(funcall-interactively #f(compiled-function (fn &rest args) (interactive nil) #<bytecode 0x1599241be4a7ac75>) transient--default-infix-command)
  #f(compiled-function (fn &rest args) (interactive '#f(compiled-function (spec) #<bytecode 0x16ce9cc417f12940>)) #<bytecode -0x52683015c5ccb0c>)(transient--default-infix-command)
  apply(#f(compiled-function (fn &rest args) (interactive '#f(compiled-function (spec) #<bytecode 0x16ce9cc417f12940>)) #<bytecode -0x52683015c5ccb0c>) transient--default-infix-command nil)
  test:--2()
  funcall-interactively(test:--2)
  call-interactively(test:--2 nil nil)
  command-execute(test:--2)

[-- Attachment #3: Type: text/plain, Size: 39 bytes --]



-- 
Best regards,
Aleksandr Vityazev

  reply	other threads:[~2024-02-21 17:20 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
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 [this message]
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=87zfvt3fap.fsf@disroot.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=69140@debbugs.gnu.org \
    --cc=avityazev@disroot.org \
    --cc=eliz@gnu.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).