zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: fndir introspection, site-packages documentation
Date: Mon, 16 Mar 2015 22:22:36 +0100	[thread overview]
Message-ID: <20150316212236.GW4524@isis.sigpipe.cz> (raw)
In-Reply-To: <20150316171312.40dbec76@pwslap01u.europe.root.pri>

# p.stephenson@samsung.com / 2015-03-16 17:13:12 +0000:
> diff --git a/NEWS b/NEWS
> index bf8969b..5b776ba 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -30,8 +30,9 @@ Changes since 5.0.0
>    exist.  Sites that set an explicit site directory can put that in
>    /etc/zshenv as before.  The intention of the new path element is to
>    increase the likelihood that locally added functions can be found with
> -  the shell running "out of the box", no matter how the shell was
> -  configured.
> +  the shell running "out of the box", unless the shell has been
> +  deliberately configured differently by the installer for some special
> +  purpose.

1. run

  ./configure --prefix=/wtf --disable-site-fndir

2. explain continuing presence of "/usr/local/share/zsh/site-functions".

btw, you've just turned the last sentence into a perfect contradiction
of the paragraph it is closing.  the first stentence still reads:
"The default $fpath/$FPATH is now designed always to include [...]"

again: [...] designed to *always* [...].

emphasis mine.  which is it?  always, or unless/provided-that?

NEWS with your change, "always" and "unless" contradicting each other:

- The default $fpath/$FPATH is now designed always to include
  /usr/local/share/zsh/site-functions.  [...]
  The intention of the new path element is to
  increase the likelihood that locally added functions can be found with
  the shell running "out of the box", unless the shell has been
  deliberately configured differently by the installer for some special
  purpose.

-- 
roman


  reply	other threads:[~2015-03-16 21:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150313224121.GO4524@isis.sigpipe.cz>
     [not found] ` <150313203904.ZM25016@torch.brasslantern.com>
     [not found]   ` <20150315021436.GQ4524@isis.sigpipe.cz>
     [not found]     ` <150315121447.ZM27996@torch.brasslantern.com>
2015-03-16  8:08       ` Roman Neuhauser
2015-03-16 16:08         ` Bart Schaefer
2015-03-16 16:46           ` Ray Andrews
2015-03-17 15:41             ` Bart Schaefer
2015-03-17 15:55               ` Ray Andrews
2015-03-16 17:05           ` Roman Neuhauser
2015-03-17 15:45             ` Bart Schaefer
2015-03-17 16:03               ` Roman Neuhauser
2015-03-16 17:13           ` Peter Stephenson
2015-03-16 21:22             ` Roman Neuhauser [this message]
2015-03-17 15:52             ` Bart Schaefer
2015-03-17 18:46               ` Peter Stephenson
2015-03-18  3:38                 ` Bart Schaefer

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=20150316212236.GW4524@isis.sigpipe.cz \
    --to=neuhauser@sigpipe.cz \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@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).