zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh list <zsh-workers@sunsite.dk>
Subject: Re: completing automounts with fake-files setting hangs zsh
Date: Sun, 25 Jan 2009 04:20:05 -0800	[thread overview]
Message-ID: <090125042005.ZM25079@torch.brasslantern.com> (raw)
In-Reply-To: <18811.39531.84244.341828@gargle.gargle.HOWL>
In-Reply-To: <m3r62sjbfj.fsf@klanderman.net>

Back in August, 2007, I wrote:
: Really this whole idea of attempting to complete things that don't
: exist yet puts a huge amount of overhead on the cases where nothing
: ever will.

Now, I get to say, "Here we go again."

On Jan 24,  5:47pm, Greg Klanderman wrote:
} 
} Is the proper way to configure completion of automounts by using the
} fake-files style setting?

On Jan 24, 10:45pm, Greg Klanderman wrote:
} 
} 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 don't know the specific method you're using to populate fake-files,
but my suggested approach is to use "zstyle -e" to filter the value
before returning it to the completion system.  Remember completion is
designed so that the shell functions typically collect all potential
matches for a given situation and then leave it up to the internals
to filter them against the command line.

So if you are able to push some of that filtering into the functions
by use of hooks like "zstyle -e", you can optimize much better than
the generic internal filters are able.


  reply	other threads:[~2009-01-25 12:20 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
2009-01-25 12:20   ` Bart Schaefer [this message]
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=090125042005.ZM25079@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).