From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7558 invoked by alias); 1 Mar 2015 18:48:49 -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: 19938 Received: (qmail 9262 invoked from network); 1 Mar 2015 18:48:36 -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=e31LXn9AOPRjwN8i++56zKoi1MXN8xXDwpIQEWdzLy0=; b=gMno0kNDcOqgkB0CtyLxEhNLq3FV1JhUMyRZykvzeZeFKzohtqcSGUuD9RP/vte04H 0ZcX6/E+ctT1ZYuo6uGpCMSvkJvzqD62vB9Az6I23NkWUxPw6U7tOx9Ms57da+YaWUrm gA4gsH3WCqeh7gADYG8jdbSBsByMIUI/QQ37g5CLnX0dmsOC8g1Q/woUZ4/8wIiVE6Md ALxIk3QwyRlyFWSTV8+VRSqG3PdOBP0f5zpN2V1myHhnvlYROdRbig9p/HaaVNbs6QxF mrZ2LY2bq+jA/DxEni3myMAcSDxmsZwXGwP8lG4IuliL8x/1utugtlO1jFtxSZXD/9A2 Q+/Q== X-Gm-Message-State: ALoCoQnvl4UUrJtOTDnsYP0i2cCEy2uVnYiP2WzIZy+ElxLD+t78FcbUMiWnpbs7ULIfvmLUSAhj X-Received: by 10.182.130.166 with SMTP id of6mr17002086obb.53.1425235713272; Sun, 01 Mar 2015 10:48:33 -0800 (PST) From: Bart Schaefer Message-Id: <150301104829.ZM16206@torch.brasslantern.com> Date: Sun, 1 Mar 2015 10:48:29 -0800 In-Reply-To: <54F345D3.9010204@eastlink.ca> Comments: In reply to Ray Andrews "Re: grammar triviality with '&&'" (Mar 1, 9:01am) References: <54F33934.2070607@eastlink.ca> <13666281425228233@web7o.yandex.ru> <54F345D3.9010204@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh Users Subject: Re: grammar triviality with '&&' MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 1, 9:01am, Ray Andrews wrote: } } I see, so it's not a 'hard' syntactic issue Actually it IS a "hard" syntactic issue, in the sense that the grammar for all *nix shells [1] both immemorial and standard, formally defines newline as equivalent to semicolon. You can demonstrate that this is the case [2] by: torch% false && ; echo AND || ; echo OR OR torch% false ; && echo AND ; || echo OR zsh: parse error near `&&' [1] I don't consider here "shells" written to use the syntax of other interpreted languages, such as shells that execute perl or php or python statements. [2] Actually bash throws a syntax error on that "&& ;", but both zsh and ksh accept it. Chet?