From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8382 invoked by alias); 1 Jan 2016 04:08:06 -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: 37470 Received: (qmail 16581 invoked from network); 1 Jan 2016 04:08:05 -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, 1 Jan 2016 05:00:52 +0100 From: Vincent Lefevre To: zsh-workers@zsh.org Subject: buggy CSH_NULL_GLOB when a pattern is at the command position Message-ID: <20160101040052.GA1808@zira.vinc17.org> 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-6542-vl-r83103 (2015-12-17) When CSH_NULL_GLOB is set and the command line contains only patterns, a "no match" error is not reported. Without CSH_NULL_GLOB: zira% [] zsh: no matches found: [] With CSH_NULL_GLOB: zira% setopt CSH_NULL_GLOB zira% [] zira% [] [] zira% [] echo foo foo but zira% echo [] zsh: no match is OK. Moreover, I wonder whether when a no-match pattern is at the command position, one should always get an error (if possible). BTW, with older zsh versions, such as 5.0.7, [] was regarded as a bad pattern (instead of a pattern that doesn't match). Has this changed on purpose? -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)