unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Observe Slowness In minibuffer-next-completion and friends
Date: Fri, 10 Nov 2023 09:00:28 -0800	[thread overview]
Message-ID: <p91o7g1a6hf.fsf@google.com> (raw)
In-Reply-To: <83y1f6xdkw.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Nov 2023 09:38:39 +0200")

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.

-- 



  reply	other threads:[~2023-11-10 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10  4:08 Observe Slowness In minibuffer-next-completion and friends T.V Raman
2023-11-10  7:38 ` Eli Zaretskii
2023-11-10 17:00   ` T.V Raman [this message]
2023-11-10  7:49 ` Juri Linkov
2023-11-10 17:01   ` T.V Raman

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=p91o7g1a6hf.fsf@google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).