From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12907 invoked by alias); 11 Feb 2015 02:35: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: 34500 Received: (qmail 11015 invoked from network); 11 Feb 2015 02:35:44 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=PYxIXZlY c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=0HtSIViG9nkA:10 a=xuazpyRhdEzvSMB_RBIA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <150210183520.ZM16470@torch.brasslantern.com> Date: Tue, 10 Feb 2015 18:35:20 -0800 In-reply-to: <54DA87F5.5090303@eastlink.ca> Comments: In reply to Ray Andrews "completion problem with '291' ok with '274'." (Feb 10, 2:36pm) References: <54DA87F5.5090303@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: completion problem with '291' ok with '274'. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 10, 2:36pm, Ray Andrews wrote: } } $ /usr/local/bin<< change to where all my builds are. } zsh-5.0.7-291-gda86d6b << most recent build here. } } $ ./zsh << no luck Mind telling us whether this is "zsh -f" and/or if you've run compinit and/or what zstyles are in play? } $ ./zsh << no luck Chances are both of these are because there actually is a binary named "zsh" in the current directory, so it's the first possible completion. } $ ./zsh-5.0.7- ... << ok 3d time, but it was as likely to } crash the xterm. FYI "crash the xterm" is not really what happens. More likely zsh has crashed and the xterm simply exited because the only process that it was running has exited. Try using "xterm -hold" so the window stays open until explicitly closed, then you'll be able to see any error messages that are generated. If the xterm goes away even with -hold, then you actually are somehow killing the xterm rather than zsh and the problem isn't ours ... } ... no completion problems with '274'. I went back and forth between } '291' and '274' and every time '291' was unstable completing, whereas } '274' was fine. Most often '291' caused the xterm to crash. Could be related to workers/34485, but you may not have directory write permission to drop a core file in /usr/local/bin so you'll have to run from inside gdb to get a stack trace. I can't repro with zsh-5.0.7-293-g0209635 but it's doubtful anything in between would have fixed a completion crash.