From: TJ Luoma <luomat@gmail.com>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: tab completion taking a _really_ long time
Date: Thu, 20 Sep 2018 18:40:10 -0400 [thread overview]
Message-ID: <CADjGqHun7rA+GPraVST2L5gQUnvWWiPVYZ6QjhJXzmFHr_C0TQ@mail.gmail.com> (raw)
In-Reply-To: <CADjGqHvCHAggY0oNj7LEZpu6YhfaOMfPTurF5zDhF3COgMtV5g@mail.gmail.com>
More info:
I tried updating zsh to a newer version, and that didn't fix the problem.
I renamed .zshenv and .zshrc so neither of them were read, and my tab
completions went back to instantaneous, so it's obviously something in
my config, but I don't know what, and obviously it didn't _used_ to do
this, so I'm still at an impasse.
--
TJ Luoma
TJ @ MacStories
Personal Website: luo.ma (aka RhymesWithDiploma.com)
Twitter: @tjluoma
On Thu, Sep 20, 2018 at 6:31 PM TJ Luoma <luomat@gmail.com> wrote:
>
> I just plugged in a computer that hasn't been used in over a year and
> ran a bunch of updates.
>
> One thing I noticed is that zsh is taking a long time (like 90
> seconds) to do tab completion for 'cd'
>
> For example, I was in my $HOME and did 'cd d' and press tab, which
> should show me Desktop, Documents, and Downloads.
>
> Instead it just sat there for 90 seconds.
>
> When I tried it again and killed it (control-c) after a few seconds,
> it reported this:
>
> Killed by signal in _path_files after 5s
>
> This was in ZSH_VERSION 5.3
>
> Any idea what I need to do to fix this?
>
> Thanks
>
> TjL
>
> ps - if more diagnostic info is needed, please let me know. I'm not
> sure what would be helpful here.
>
>
> --
> TJ Luoma
> TJ @ MacStories
> Personal Website: luo.ma (aka RhymesWithDiploma.com)
> Twitter: @tjluoma
next prev parent reply other threads:[~2018-09-20 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 22:31 TJ Luoma
2018-09-20 22:40 ` TJ Luoma [this message]
2018-09-21 1:41 ` TJ Luoma
2018-09-21 2:19 ` Bart Schaefer
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=CADjGqHun7rA+GPraVST2L5gQUnvWWiPVYZ6QjhJXzmFHr_C0TQ@mail.gmail.com \
--to=luomat@gmail.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).