zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Neuhauser <neuhauser@sigpipe.cz>, zsh-users@zsh.org
Subject: Re: fndir introspection, site-packages documentation
Date: Fri, 13 Mar 2015 20:39:04 -0700	[thread overview]
Message-ID: <150313203904.ZM25016@torch.brasslantern.com> (raw)
In-Reply-To: <20150313224121.GO4524@isis.sigpipe.cz>

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.


  reply	other threads:[~2015-03-14  3:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 22:41 Roman Neuhauser
2015-03-14  3:39 ` Bart Schaefer [this message]
2015-03-15  2:14   ` Roman Neuhauser
2015-03-15 19:14     ` Bart Schaefer
2015-03-16  9:36       ` patches format " Daniel Shahaf
2015-03-16 10:01         ` Peter Stephenson

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=150313203904.ZM25016@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=neuhauser@sigpipe.cz \
    --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).