From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13732 invoked by alias); 21 Oct 2015 22:16:08 -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: 36910 Received: (qmail 17198 invoked from network); 21 Oct 2015 22:16:07 -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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=goDDQjmBRQkvI6jLoakZZZdVyvIzEzURaghbZad2Z1A=; b=PPwznClh/pSCK35U7vL6UT4Jxh3hYE6na5/VjQ37Xi6hguWKS+VZQjvps3T9dizNtG YIZXAw1ra9Be0fJz8Lz83/FC1UMwJe+BIrwMTAUes3Fmzv/OETjfVeWTz8MFzddKDQSy 3Yz9JH0SNpv9SG8AJLU3GwFypK+R1Iu2Q3nWg7jSPFaaP08Rr9829jsJyU4AMy5HuT1Q oFahIYjmFqnrAvxqnaPzJsQtwMBZ4Hl54r4as1xOmBSZ1ufYQPigjkZnA/31aX98imJO ImW7RKWv3Q0qdLGVbjS7TE2J35W6WmvPREV/QoE4TGsAtC9IyNhXfavbpSNHsk1OHCDJ 3OCA== X-Gm-Message-State: ALoCoQkko+15y6ugsaqzCm8wOVhR5z0T6L1MttEGuU6m3SiGcwwNchywfR/jZwkjRkgWRLQ/PRKF X-Received: by 10.182.29.99 with SMTP id j3mr7850300obh.1.1445465763857; Wed, 21 Oct 2015 15:16:03 -0700 (PDT) From: Bart Schaefer Message-Id: <151021151600.ZM5429@torch.brasslantern.com> Date: Wed, 21 Oct 2015 15:16:00 -0700 In-Reply-To: Comments: In reply to Bart Schaefer "Re: Bug report: zsh crashes when expanding long command from history." (Oct 21, 3:04pm) References: <56261BBA.9000805@allegrodvt.com> <151020103005.ZM1642@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: Bug report: zsh crashes when expanding long command from history. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 21, 3:04pm, Bart Schaefer wrote: } } I suppose this might still break on a single word more than 64k } characters long, but it'll break by returning the substring of the } command line rather than by crashing. That should say "wrong substring". } (This diff might get garbled, I'm not using my regular email client.) Yep, it did. Sorry.