unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: why is my cd command on eshell on Windows so slow?
Date: Fri, 16 Apr 2021 21:59:55 +0300	[thread overview]
Message-ID: <83r1javyvo.fsf@gnu.org> (raw)
In-Reply-To: <86r1jaqdia.fsf@protonmail.com> (message from Wayne Harris via Users list for the GNU Emacs text editor on Fri, 16 Apr 2021 15:40:29 -0300)

> Date: Fri, 16 Apr 2021 15:40:29 -0300
> From:  Wayne Harris via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> So when I cd into a directory, I get:
> 
> %cd dir/
> 0.001 secs
> %
> 
> However, it actually took about 3 seconds for me to get my prompt back.
> There is something before cd actually operates (or afterwards) that
> makes me wait --- *sometimes*.  If I immediately ``cd ..'' and then cd
> into dir/ once again, it's pretty fast.
> 
> %which cd
> eshell/cd is a compiled Lisp function in `em-dirs.el'
> %
> 
> Can you point me in the right direction?  This is a Windows system.

Profile it, then look at the profile to see what takes most of the
time.



  reply	other threads:[~2021-04-16 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 18:40 why is my cd command on eshell on Windows so slow? Wayne Harris via Users list for the GNU Emacs text editor
2021-04-16 18:59 ` Eli Zaretskii [this message]
2021-04-16 20:14   ` Wayne Harris via Users list for the GNU Emacs text editor
2021-04-16 21:14     ` Stefan Monnier
2021-04-17  0:10       ` Wayne Harris via Users list for the GNU Emacs text editor
2021-04-17  8:28         ` Wayne Harris via Users list for the GNU Emacs text editor
2021-04-17 14:08           ` Stefan Monnier
2021-04-17 14:32             ` Óscar Fuentes
2021-04-17 14:39               ` Eli Zaretskii
2021-04-17 14:56                 ` Óscar Fuentes
2021-04-17 15:05                   ` Eli Zaretskii
2021-04-17 14:41               ` Stefan Monnier

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=83r1javyvo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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. 
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).