[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Observe Slowness In minibuffer-next-completion and friends
|
From: |
T.V Raman |
|
Subject: |
Re: Observe Slowness In minibuffer-next-completion and friends |
|
Date: |
Fri, 10 Nov 2023 09:00:28 -0800 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
It's emacs with all custom options as I have in my environment; reducing
it to emacs -q then turning off the new minibuffer-completion nav will
take some time.
For what it's worth, I turned on debug-on-quit and hit C-g during the
slowness but it appears that emacs in that state is not accepting any
input -- ie C-g quit and entered the debugger only after the hankiness
was done.>> Date: Thu, 09 Nov 2023 20:08:10 -0800
>> From: "T.V Raman" <raman@google.com>
>>
>> This appears to be new as of this afternoon's update on Git:
>>
>> Type:
>> C-h f next- <tab>
>> Then press down-arrow to move to next completion; the completion list
>> appears to be not active for about a second. I already tried setting
>> completion-highlight-face to nil, but the slowness remains; from
>> memory this feels new compared to yesterday
>
> Is this in "emacs -Q"? If not, please tell which customizations are
> necessary for reproducing this starting from "emacs -Q". Because in
> "emacs -Q" <DOWN> arrow is not supposed to move to the next completion
> candidate.
--