zsh-users
 help / color / mirror / code / Atom feed
From: lists <lists@kalama.no-ip.org>
To: zsh-users@sunsite.dk
Subject: Re: Avoid LDAP hit during completion
Date: Tue, 7 Jun 2005 07:33:01 -0500	[thread overview]
Message-ID: <CBF3A7F3-F1F5-4094-BC87-A9CAB8A7B95A@kalama.no-ip.org> (raw)
In-Reply-To: <1050607102405.ZM23139@candle.brasslantern.com>

Bart, this may be true, but I've used OS X 10.3 workstations bound to  
an LDAP domain containing 2000+ users and haven't seen problems like  
this unless I do something like 'chown<TAB>'.  Odd that Chris would  
run into it and I wouldn't if it were strictly due to user lookups.   
Chris, Peter's suggestions (adding xtrace to _comp_setup) sounds like  
a good thing to try.

-Ryan

On Jun 7, 2005, at 5:24 AM, Bart Schaefer wrote:

> On Jun 7, 10:26am, Peter Stephenson wrote:
> } Subject: Re: Avoid LDAP hit during completion
> }
> } Chris Wong wrote:
> } > For some reason, whenever I start a zsh shell, the first  
> completion
> } > will trigger many many LDAP lookup.
> }
> } Are you using the new completion system (with compinit)?  The  
> best way
> } of tracking this down would be to see what the completion scripts  
> are
> } doing.
>
> It's almost certainly the zsh/parameter module looking up all possible
> user names on the system to implement the $userdirs variable, which is
> used by several of the completion functions including _expand and the
> more obvious _users and _tilde_files.
>
> Unfortunately there's no simple way to disable this.
>


  reply	other threads:[~2005-06-07 12:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 17:25 Chris Wong
2005-06-06 18:16 ` lists
2005-06-06 18:38   ` Chris wong
2005-06-07  9:26 ` Peter Stephenson
2005-06-07 10:24   ` Bart Schaefer
2005-06-07 12:33     ` lists [this message]
2005-06-07 16:27   ` Chris Wong
2005-06-07 23:19     ` Chris wong
2005-06-08  0:52       ` lists
2005-06-08  1:32         ` William Scott
2005-06-08  2:49           ` Bart Schaefer
2005-06-08  9:35       ` Peter Stephenson
2005-06-16  6:33         ` Chris Wong
2005-06-07 15:41 ` William Scott

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=CBF3A7F3-F1F5-4094-BC87-A9CAB8A7B95A@kalama.no-ip.org \
    --to=lists@kalama.no-ip.org \
    --cc=zsh-users@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).