From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22218 invoked by alias); 14 Mar 2015 03:39:14 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20008 Received: (qmail 16790 invoked from network); 14 Mar 2015 03:39:12 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=fFxXjPeuauxkx2lrrcxuH5vm4f+hYJDm3Dn5atN5p5s=; b=kh2utmH9+DQ2kQJvEx+i8C5XhbummpRC4IWM9X2vAXHUese+EdNQuP+ermSOiYQi/7 qcSlMtbN/QlffFlhYAg3HJuQ5pqNBpkgNfsbpiGfqzeqjVBymUtlJzbFZdAESMkGwRbz kZjB1yU3AsM6A2WEFS+S9uqJTBiZ9XXNn6dBpYCWQywR0/X/YFyxCxGm/LzTTeTNpL9I nobRAGZkreHd5qvoBP4vq0OuiTKZZxaOgzJgG8tsZxxamXAvup3wBgzgQb+dYxnkT6FT kRkd/erDuyw+ZjP5wWIfP2Uy0Aw9RbX7dZA8QnGoH4sGNeAQX6ACOBuJS1Z5+tVaGi7x olNA== X-Gm-Message-State: ALoCoQkU3q02m/CHXxhKyszud73jrh/vUoYIWvOEuRJuxyL5BQDMbAaYCeY0tkryk7Lo+TleOjUu X-Received: by 10.182.22.167 with SMTP id e7mr39620234obf.31.1426304347627; Fri, 13 Mar 2015 20:39:07 -0700 (PDT) From: Bart Schaefer Message-Id: <150313203904.ZM25016@torch.brasslantern.com> Date: Fri, 13 Mar 2015 20:39:04 -0700 In-Reply-To: <20150313224121.GO4524@isis.sigpipe.cz> Comments: In reply to Roman Neuhauser "fndir introspection, site-packages documentation" (Mar 13, 11:41pm) References: <20150313224121.GO4524@isis.sigpipe.cz> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Roman Neuhauser , zsh-users@zsh.org Subject: Re: fndir introspection, site-packages documentation MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 13, 11:41pm, Roman Neuhauser wrote: } } is there a way to get at the value "fndir" ended up having in configure? Sort of. The trouble is that if --enable-function-subdirs has been used for configure, there isn't really a useful scalar value of fndir, you have to have the whole $fpath array. If you ignore that complication, you can do sitefndir=$(zsh -fc 'case $#fpath in \ (1) print $fpath;; (2) print $fpath[2];; (*) print $fpath[2]:h;; esac') } apropos! } } there's a *single* occurrence of "site-functions" in zshall(1) Yes, see complications above ... it's nearly impossible to know what to refer to in the doc when you allow the packager to relocate things to anywhere (or a whole list of anywheres) that he wants. An end user isn't supposed to need to know about site-functions (even the mention under zsh/newuser is more for the administrator installing the newuser function than for the user invoking it). The user just needs to refer to what shows up in the default $fpath, and know that he can add his own directories to it. I suppose ideally we'd have a separate doc section for adminstrative miscellany.