From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 712 invoked by alias); 20 Sep 2012 14:32:05 -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: 30690 Received: (qmail 20963 invoked from network); 20 Sep 2012 14:32:01 -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, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at csr.com does not designate permitted sender hosts) Date: Thu, 20 Sep 2012 15:26:13 +0100 From: Peter Stephenson To: Mailing-list zsh-workers Subject: Re: Completion and REPORTTIME Message-ID: <20120920152613.71262042@pwslap01u.europe.root.pri> In-Reply-To: <120920071549.ZM26034@torch.brasslantern.com> References: <120920071549.ZM26034@torch.brasslantern.com> Organization: Cambridge Silicon Radio X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.101.10.18] X-Scanned-By: MailControl 9446.0 (www.mailcontrol.com) on 10.71.0.143 On Thu, 20 Sep 2012 07:15:49 -0700 Bart Schaefer wrote: > We should add "local REPORTTIME=0" to _comp_setup in Completion/compinit, > but that only helps for completions that go through _main_complete > (which admittedly is most of them). That doesn't actually fix the problem, because the job that calls _main_complete hasn't terminated at that point, and when it does REPORTTIME is restored. -- Peter Stephenson Software Engineer Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog