From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1761 invoked by alias); 29 May 2017 04:04:47 -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: 41175 Received: (qmail 21634 invoked from network); 29 May 2017 04:04:47 -0000 X-Qmail-Scanner-Diagnostics: from rcpt-expgw.biglobe.ne.jp by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(133.208.98.1):SA:0(-0.7/5.0):. Processed in 1.464767 secs); 29 May 2017 04:04:47 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: takimoto-j@kba.biglobe.ne.jp X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf01.biglobe.ne.jp designates 133.208.98.1 as permitted sender) X-Biglobe-Sender: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: zsh 5.3.1 crashes on completion From: "Jun T." In-Reply-To: <20170526101957.126606d2@pwslap01u.europe.root.pri> Date: Mon, 29 May 2017 13:04:37 +0900 Content-Transfer-Encoding: 7bit Message-Id: <0D144B45-22EE-452A-AA6B-44F1AF914B54@kba.biglobe.ne.jp> References: <170511141903.ZM13639@torch.brasslantern.com> <20170512161603.GA16688@fujitsu.shahaf.local2> <783A691B-B69F-4673-B237-B316CEF26346@remrain.com> <170513112313.ZM14712@torch.brasslantern.com> <20170515102819.39284ef6@pwslap01u.europe.root.pri> <170515133354.ZM20191@torch.brasslantern.com> <20170516104831.14aa23c6@pwslap01u.europe.root.pri> <20170516120527.572a5cc9@pwslap01u.europe.root.pri> <20170526101957.126606d2@pwslap01u.europe.root.pri> To: "zsh-workers@zsh.org" X-Mailer: Apple Mail (2.1510) X-Biglobe-Spnum: 60305 On 2017/05/26, at 18:19, Peter Stephenson wrote: > > The first change is the actual fix, making the DPUTS as well as > the other new framework redundant. I've been using this for a day or two without any problems.