From: Nikolai Weibull <now@disu.se>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: [Feature suggestion] (user configurable) timeout for generating completion lists
Date: Thu, 23 Jan 2014 13:04:55 +0100 [thread overview]
Message-ID: <CADdV=MsdfHUKDVy1dLbZ-d19cAEpGuDxzsKPd3Cy6imJ1Lo_8Q@mail.gmail.com> (raw)
In-Reply-To: <140122000435.ZM1516@torch.brasslantern.com>
On Wed, Jan 22, 2014 at 9:04 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Jan 20, 4:13pm, Arseny Tolmachev wrote:
> }
> } Sometimes you press [Tab] by instinct when in directory that is
> } network-mounted and has some millions files in it.
> } In this situation zsh basically ignores the [Ctrl+C] and don't respond to
> } anything for a bit of time.
> There are two possible situations here. (Probably more than two, but
> only two likely ones.)
> (1) The shell process is actually in "disk wait" condition, blocked to
> wait for the NFS volume to respond. If this is the case, there's not
> a lot that can be done; any timeout that might be set up will also be
> held until the disk condition clears.
Time to delegate completion to a subprocess? That’d make it possible
to use Zsh completions from outside the shell as well.
next prev parent reply other threads:[~2014-01-23 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 7:13 Arseny Tolmachev
2014-01-22 8:04 ` Bart Schaefer
2014-01-23 12:04 ` Nikolai Weibull [this message]
2014-01-24 1:16 ` Bart Schaefer
2014-01-24 9:00 ` Nikolai Weibull
2014-01-25 20:09 ` _git and partial completion, again Bart Schaefer
2014-01-24 14:46 ` [Feature suggestion] (user configurable) timeout for generating completion lists Greg Klanderman
2014-01-25 20:49 ` Bart Schaefer
2014-01-29 16:29 ` Greg Klanderman
2014-02-25 15:35 ` Greg Klanderman
2014-01-22 13:51 ` Shawn Wilson
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='CADdV=MsdfHUKDVy1dLbZ-d19cAEpGuDxzsKPd3Cy6imJ1Lo_8Q@mail.gmail.com' \
--to=now@disu.se \
--cc=schaefer@brasslantern.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).