From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18540 invoked by alias); 27 Aug 2015 04:55:02 -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: 36287 Received: (qmail 26590 invoked from network); 27 Aug 2015 04:55:01 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+pweT+k0n467gaeczTtX+HOp0IUZXWp+RXGrKJg9Evo=; b=azBIM83HIROs/MKJ+SaFRdJLGLSvnfzB+5+jwM01k4wKVJdwsXF4XsS8F8HGRTTa+/ yrvJfHWKB0dfAP4nbDDhxnomuBi5SOMopEd1ssS4tAqOqtNCZJZBw2WdC6VcoIYNOLYY 5/TUDWtUtON5YEdESu33XCR2lcleEDarFD+vmCqycKiSy1WX4CMAIN2Yf42QOhLr9JNF zKA1miejpyWGsC1Raa+IPqbfvjJUDKZxLGGNta7MkgkLcQC+viMsZAuJrj/fMDUHYYbD wlhXe9OZWiolGbKc7ekDZkTQvkUInl4YFumntb+ZlLLjDUHBk/524frzj8Ah3sDgU0TL 7HrQ== MIME-Version: 1.0 X-Received: by 10.140.233.7 with SMTP id e7mr3557061qhc.79.1440651297115; Wed, 26 Aug 2015 21:54:57 -0700 (PDT) In-Reply-To: <150826214729.ZM12037@torch.brasslantern.com> References: <20150826053928.GD19027@tarsus.local2> <150826111808.ZM30185@torch.brasslantern.com> <150826213532.ZM31157@torch.brasslantern.com> <150826214729.ZM12037@torch.brasslantern.com> Date: Thu, 27 Aug 2015 06:54:57 +0200 Message-ID: Subject: Re: Completion of prefix redirections is -command- instead of -redirect- From: Mikael Magnusson To: Bart Schaefer Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On Thu, Aug 27, 2015 at 6:47 AM, Bart Schaefer wrote: > On Aug 26, 9:35pm, Bart Schaefer wrote: > } > } Does this do it? > > To answer my own question, no, it doesn't ... or at least not entirely. > > Both WITH and WITHOUT the change in 36285, completing after this: > > % ls < ; > > completes files rather than commands. I suppose if you've botched the > syntax you have no right to expect sanity, and the foregoing hasn't > changed since 5.0.7, so we're no worse off. Yeah, it's better than either with or without the 36285 patch, but still doesn't handle all cases, < gives files (correct) ; gives commands (correct) < ; gives commands (correct) foo < ; gives files (wrong-ish) ; < gives commands (wrong) foo=bar; < gives commands (wrong, presumably same case as the above) ; < : gives commands (correct) ; < : : gives files (correct) Is there any reason we can't just reset state to 'this is a new command' when we see an unquoted solo semicolon? Or is determining that this is the case in fact the trouble? -- Mikael Magnusson