GNU bug report logs - #36733
27.0.50; Eshell taking long time to enter directory after TAB completion

Previous Next

Package: emacs;

Reported by: Jean Louis <bugs <at> gnu.support>

Date: Fri, 19 Jul 2019 21:24:02 UTC

Severity: minor

Found in version 27.0.50

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jean Louis <bugs <at> gnu.support>
Cc: 36733 <at> debbugs.gnu.org
Subject: bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion
Date: Sat, 20 Jul 2019 13:08:13 +0300
> Date: Sat, 20 Jul 2019 11:07:20 +0200
> From: Jean Louis <bugs <at> gnu.support>
> Cc: 36733 <at> debbugs.gnu.org
> 
> This is what I have done:
> 
> $ emacs -Q
> 
> Then I started profiler, and within Emacs I went
> to em-dirs.el.gz and clicked L to load the file
> 
> Then I started eshell and did following:
> 
> Welcome to the Emacs shell
> 
> ~ $ cd Programming/
> ~/Programming $ cd ..
> ~ $ cd Documents/
> ~/Documents $ cd ..
> ~ $ cd tmp
> ~/tmp $ cd ..
> ~ $ cd tmp/
> ~/tmp $ cd ..
> ~ $ cd Media/
> ~/Media $
> 
> Here is the report:

Thanks.  I don't see eshell/cd anywhere in this report, so it's hard
to glean anything useful from the profile.

Please modify your procedure as follows:

  emacs -Q
  M-x load-library RET em-dirs.el RET
  M-x eshell RET
  M-x profiler-start RET RET
  ~ $ cd Programming/
  ~/Programming $ cd ..
  ~ $ cd Documents/
  ~/Documents $ cd ..
  ~ $ cd tmp
  ~/tmp $ cd ..
  ~ $ cd tmp/
  ~/tmp $ cd ..
  ~ $ cd Media/
  ~/Media $
  M-x profiler-report RET

IOW, start the profiler just before you start the Eshell commands.

If the results don't show eshell/cd in the profile, or if the
percentage for that is too low, perhaps repeat the recipe with more
"cd" commands.

Thanks.




This bug report was last modified 1 year and 50 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.