From: Greg Klanderman <gak@klanderman.net>
To: zsh-workers@sunsite.dk
Subject: Re: completing automounts with fake-files setting hangs zsh
Date: Sat, 24 Jan 2009 22:45:36 -0500 [thread overview]
Message-ID: <m3r62sjbfj.fsf@klanderman.net> (raw)
In-Reply-To: <18811.39531.84244.341828@gargle.gargle.HOWL> (Greg Klanderman's message of "Sat, 24 Jan 2009 17:47:07 -0500")
Further investigation seems to indicate that the problem lies in it
stat'ing all those "fake" files, and some of those stats are taking a
very long time. Is there some way to have it not do that? I guess I
really need a "fake-directories" style so it can not stat them, but
assume the automounts are directories.
thanks,
Greg
next prev parent reply other threads:[~2009-01-25 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 22:47 Greg Klanderman
2009-01-25 3:45 ` Greg Klanderman [this message]
2009-01-25 12:20 ` Bart Schaefer
2009-01-25 16:40 ` Greg Klanderman
2009-01-25 18:56 ` Greg Klanderman
2009-01-26 6:11 ` Phil Pennock
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=m3r62sjbfj.fsf@klanderman.net \
--to=gak@klanderman.net \
--cc=zsh-workers@sunsite.dk \
/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).