From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28987 invoked by alias); 19 Sep 2014 03:22:31 -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: 19107 Received: (qmail 11678 invoked from network); 19 Sep 2014 03:22:29 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 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=Uh9vYAUEeCXjkR3KDYmywJyGAnrDu+h8pA/IBFp0wxw=; b=Ffe4nInp5OvonCzlyzO0L8lixEHl1lOXwyGSBLvXGDiI4qZN7Xyy8OK10owSRcl8+l NXUTrYBHCW/MWwHpPpzLXxDOZRS5PuhSZad0Qg6egTkakq10TKe4u0Q6VxfLWlw5gIFu FAw6a1P+kRmWfAPeGKgKhsynDckA+LZ2fhhlKxGS4ihfDczORI4luAG1hnh9PvKn6UQ3 7IetQ9WCYUSJfHBEzZCndOt+l4OtIzu9XwjD3UmrzGs9grYjAe9cnoIWTusNbps6NtWQ c/7FoHUo97zYgWC4zOwQkV083bKh9uw1Smo+Yg5BXryFABlB9x9XrA3HhdFqIc6ZMH/2 1Wxw== MIME-Version: 1.0 X-Received: by 10.50.153.83 with SMTP id ve19mr53502974igb.4.1411096943023; Thu, 18 Sep 2014 20:22:23 -0700 (PDT) In-Reply-To: <140918190130.ZM8366@torch.brasslantern.com> References: <2002755.9ryFYYVtTN@note> <5418786F.8030001@thregr.org> <140916175124.ZM5742@torch.brasslantern.com> <54194198.2010607@thregr.org> <140917085133.ZM6725@torch.brasslantern.com> <541AA918.8060503@thregr.org> <140918093602.ZM7963@torch.brasslantern.com> <140918190130.ZM8366@torch.brasslantern.com> Date: Fri, 19 Sep 2014 05:22:22 +0200 Message-ID: Subject: Re: rsync --progress stops completion From: Mikael Magnusson To: Bart Schaefer Cc: Zsh Users Content-Type: text/plain; charset=UTF-8 On 19 September 2014 04:01, Bart Schaefer wrote: > On Sep 18, 9:36am, Bart Schaefer wrote: >> >> We could also consider this (I'm not sure what unexpected side-effects >> there might be, particularly for completers that try multiple calls >> to _arguments): >> >> else >> + _message "$service cannot parse command line" >> return 1 >> fi > > Indeed, the above causes a spurious warning from "su" completion. So > I don't think I'll be committing that. > > While trying out a few completion functions that use repeated calls to > _arguments, I encountered some miscellaneous bugs (I didn't try enough > functions to pretend this is even close to all the bugs that may be > lurking): > > _cryptsetup - offers all options when completing after "-", but will > only allow one option to appear on the command line, as if all options > are mutually exclusive. > > _quilt - returns 0 even when it finds no completions, breaking the > zstyle fallback I suggested. > > _bzr - complains to stderr if bzr is not in $path > > _surfraw - complains to stderr if surfraw is not in $path > > The latter two make me think that _call_program should do something > with stderr -- probably just throw it away, rather than make every > caller add its own redirection. If we're collecting _arguments bugs here, I noticed yesterday that while typeset - correctly completes options, typing something after and then going back to the dash to complete, eg typeset - foo is written here just inserts a = sign. -- Mikael Magnusson