From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20903 invoked by alias); 1 Mar 2015 17:01:25 -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: 19937 Received: (qmail 1338 invoked from network); 1 Mar 2015 17:01:13 -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,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_3gmFRaawBQx/DaXEd1cXJA)" X-Authority-Analysis: v=2.1 cv=T/C1EZ6Q c=1 sm=1 tr=0 a=v3jdlwE+mftNnR1sUa1KMQ==:117 a=v3jdlwE+mftNnR1sUa1KMQ==:17 a=VNsaWKQvMhEA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10 a=gZbpxnkM3yUA:10 a=tM86BLJ-sKUmo6VWMJoA:9 a=pvA44qeTxYYA:10 a=vaJtXVxTAAAA:8 a=I5UsoG0cLw7lwyOtOyIA:9 a=_W_S_7VecoQA:10 Message-id: <54F345D3.9010204@eastlink.ca> Date: Sun, 01 Mar 2015 09:01:07 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.4.0 To: ZyX , zsh Users Subject: Re: grammar triviality with '&&' References: <54F33934.2070607@eastlink.ca> <13666281425228233@web7o.yandex.ru> In-reply-to: <13666281425228233@web7o.yandex.ru> --Boundary_(ID_3gmFRaawBQx/DaXEd1cXJA) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 03/01/2015 08:43 AM, ZyX wrote: > > Each of the lines is a sequence of `zle self-insert` followed by `zle accept-line`. In first and third cases it is possible to, based on parser state, determine that more input is required. In the second it is a complete command on the first line. I see, so it's not a 'hard' syntactic issue, the limitation is in the rules for look ahead, namely that if the parser feels it has a complete sentence then it never looks at the next line. OK, that's a crisp answer. Given how complex all that stuff is, I'd not even dare ask for that to be touched, something would break for sure. (Me, I've always preferred breaking lines before && and ||, but it's hardly important.) --Boundary_(ID_3gmFRaawBQx/DaXEd1cXJA)--