From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25207 invoked by alias); 20 Nov 2015 11:44:59 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 37167 Received: (qmail 11750 invoked from network); 20 Nov 2015 11:44:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_PCNT autolearn=no autolearn_force=no version=3.4.0 Date: Fri, 20 Nov 2015 12:44:56 +0100 From: Vincent Lefevre To: zsh-workers@zsh.org Subject: WARN_CREATE_GLOBAL and parameters used by the shell Message-ID: <20151120114456.GA24924@cventin.lip.ens-lyon.fr> Mail-Followup-To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailer-Info: https://www.vinc17.net/mutt/ User-Agent: Mutt/1.5.24-6525-vl-r83103 (2015-11-18) I think that when WARN_CREATE_GLOBAL is set, one should get no warnings for parameters used by the shell, as their intent is to be global. For instance: cventin% setopt WARN_CREATE_GLOBAL cventin% foo() { RPS1="<" } cventin% foo foo: scalar parameter RPS1 created globally in function There is no such problem with PS1, PS2, PS3 and PS4, probably because they are already set by zsh. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)