From: Jim Porter <jporterbugs@gmail.com>
To: bugs@gnu.support, 36733@debbugs.gnu.org
Subject: bug#36733: 27.0.50; Eshell taking long time to enter directory after TAB completion
Date: Sun, 28 Jul 2024 13:06:19 -0700 [thread overview]
Message-ID: <29cca35d-d050-d872-c751-c848700c491c@gmail.com> (raw)
In-Reply-To: <86ftn1iuuf.fsf@protected.rcdrun.com>
On 7/19/2019 2:21 PM, Jean Louis wrote:
>
> I have observed that if I write in Eshell:
>
> $ cd Documents
>
> That it enters the directory quickly.
>
> But if I write:
>
> $ cd Docum TAB
>
> it expands into
>
> $ cd Documents/
>
> then when I press ENTER it is taking sometimes 1 second or few seconds
> just to enter the directory.
>
> This also happens if inside of directory there is just one file.
In the intervening 5 years, there have been many improvements to both
Eshell and Pcomplete. Are you still able to reproduce this? I tried
locally, and everything seems ok to me, but maybe I'm just missing some
essential step.
next prev parent reply other threads:[~2024-07-28 20:06 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
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 [this message]
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=29cca35d-d050-d872-c751-c848700c491c@gmail.com \
--to=jporterbugs@gmail.com \
--cc=36733@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).