all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: 73592@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#73592: 30.0.91; delayed output with completion preview mode
Date: Thu, 03 Oct 2024 08:17:44 +0200	[thread overview]
Message-ID: <m1setd7lrr.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <87y136mnv7.fsf@librehacker.com> (Christopher Howard's message of "Wed, 02 Oct 2024 09:11:08 -0800")

Christopher Howard <christopher@librehacker.com> writes:

> Here is the memory profile report, focusing on the completion-preview functions:
>
[...]
>
> And here is the CPU report:
>
> ```
>         1318  53% + command-execute
>          932  37%   Automatic GC
>          200   8% - completion-preview--post-command
>          200   8%  - completion-preview--show
>          200   8%   - completion-preview--try-update
>          200   8%    - completion-preview--update
>          200   8%     - run-hook-wrapped
>          200   8%      - completion-preview--capf-wrapper
>          184   7%       - completion-preview--try-table
>          180   7%        - completion-all-completions
>          180   7%         - completion--nth-completion
>           92   3%          - #<byte-code-function 080>
>           92   3%           - completion--twq-all
>           92   3%            - mapcar
>           88   3%             - #<byte-code-function 011>
>           80   3%              - comint-quote-filename
>           80   3%               - regexp-opt-charset
>           24   0%                - map-char-table
>           16   0%                 - #<byte-code-function 43C>
>           16   0%                    format
>            4   0%                  format
>           88   3%          - seq-some
>           88   3%           - seq-do
>           88   3%            - mapc
>           88   3%             - #<byte-code-function 0BE>
>           88   3%              - #<byte-code-function 0AF>
>           88   3%               - completion-basic-all-completions
>           88   3%                - completion-pcm--all-completions
>           88   3%                 - all-completions
>           88   3%                  - #<byte-code-function 3C8>
>           88   3%                   - #<byte-code-function 3E2>
>           68   2%                      all-completions
>           12   0%                      file-name-all-completions
>            8   0%                    - pcomplete-uniquify-list
>            8   0%                     - sort
>            4   0%                        #<primitive-function string-lessp>
>            4   0%        + minibuffer--sort-by-length-alpha
>           16   0%       + pcomplete-completions-at-point
>           28   1% + redisplay_internal (C function)
>            4   0% + timer-event-handler
>            0   0%   ...
> ```

Thanks, I get a similar profile, but no perceivable delay, so I'm not
sure it helps us pin down the problem that you're seeing.  

The fact that you don't see a delay with emacs -Q is a good lead, please
try to create a minimal configuration that reproduces this for you and
we can investigate from there.

If anybody else experiences such issues (significant delay after typing
a character before it appears), please let us know.


Thanks,

Eshel





  reply	other threads:[~2024-10-03  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 23:04 bug#73592: 30.0.91; delayed output with completion preview mode Christopher Howard
2024-10-02  6:42 ` Eli Zaretskii
2024-10-02  7:24   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-02 17:11     ` Christopher Howard
2024-10-03  6:17       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-04  0:07       ` Dmitry Gutov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1setd7lrr.fsf@dazzs-mbp.home \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73592@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    --cc=eliz@gnu.org \
    --cc=me@eshelyaron.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.