unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36733@debbugs.gnu.org
Subject: bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion
Date: Sat, 20 Jul 2019 09:50:07 +0200	[thread overview]
Message-ID: <20190720075007.GA24669@protected.rcdrun.com> (raw)
In-Reply-To: <83tvbhtbus.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2019-07-20 09:16]:
> Doesn't happen here.  I suggest to start a CPU profiler, perform this
> many times, then show the profile, completely expanded.  For best
> results, load em-dirs.el as an uncompiled file, before doing this
> experiment.

Help me how to start CPU profiler? Is it gprof?






  reply	other threads:[~2019-07-20  7:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 21:21 bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion Jean Louis
2019-07-20  7:16 ` Eli Zaretskii
2019-07-20  7:50   ` Jean Louis [this message]
2019-07-20  8:31     ` Eli Zaretskii
2019-07-20  9:07       ` Jean Louis
2019-07-20 10:08         ` Eli Zaretskii
2019-07-20 10:31           ` Jean Louis
2019-07-20 10:55             ` Eli Zaretskii
2019-07-20 15:28               ` Jean Louis
2019-07-20 15:56                 ` Eli Zaretskii
2019-07-20 16:22                   ` Jean Louis
2019-07-20 16:40                     ` Eli Zaretskii
2020-02-29  1:30 ` bug#36733: (no subject) Ivan Kozlov
2020-02-29  9:40   ` Ivan Kozlov
2020-02-29  3:51 ` bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion Ivan Kozlov
2020-02-29  6:40   ` Ivan Kozlov
2020-02-29  7:24     ` Ivan Kozlov
2020-02-29  7:56       ` Ivan Kozlov
2020-02-29  9:02         ` Ivan Kozlov
2020-02-29  9:33         ` Ivan Kozlov
2024-07-28 20:06 ` Jim Porter
2024-07-30 16:16   ` Jean Louis

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=20190720075007.GA24669@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=36733@debbugs.gnu.org \
    --cc=eliz@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).