From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18638 invoked by alias); 12 Dec 2014 10:01:17 -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: 33953 Received: (qmail 7723 invoked from network); 12 Dec 2014 10:01:15 -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=CkdkTu03J7H5LRVsCkHZjKVl06C+5+278U2m0d3f+dM=; b=CQjYJilbD2qVKzb/nxV2KDv4Kzk2hR80cMIEup3LPM5Rsyg7EUaTvtWR5XSc8XO3GL k6TOGtjN7Dj2kiMsE8vVIE/LPTKnPOpYXvpH+ax2QeeklqOjOK8Ig1ZODMODE9sHuyEe usjhhLMF33HPk4IYEC/q325WGbpc4/4TiKqSEWZx54KmBTdjkxa/0BuIQLgX/ZKFRKzJ lPhR/sb3ClXJL9h+C3oG5YcolD5JtT2cHJq6KD7ro8r0ckbJ40RYBGFaCVLmDEXY7iVb Mt2mO2zH+UHqWX2dkDnUVpVg+/KCYIOZjYfIxYbTWnIQW541MghL/UYLdC/D8v3+/lDa CIww== MIME-Version: 1.0 X-Received: by 10.107.128.87 with SMTP id b84mr12428260iod.42.1418378470557; Fri, 12 Dec 2014 02:01:10 -0800 (PST) In-Reply-To: <548AB9F4.9080608@realraum.at> References: <54655C0F.8020308@realraum.at> <5487D8CD.6080603@realraum.at> <141210091937.ZM11958@torch.brasslantern.com> <548AB9F4.9080608@realraum.at> Date: Fri, 12 Dec 2014 11:01:10 +0100 Message-ID: Subject: Re: zsh history bug ? From: Mikael Magnusson To: Bernhard Tittelbach Cc: Bart Schaefer , "zsh-workers@zsh.org >> Zsh hackers list" Content-Type: text/plain; charset=UTF-8 On Fri, Dec 12, 2014 at 10:48 AM, Bernhard Tittelbach wrote: > Am 2014-12-10 um 18:19 schrieb Bart Schaefer: >> On Dec 10, 6:23am, Bernhard Tittelbach wrote: >> >> I'm not able to reproduce this on MacOS (the platform where the bug >> originally was reported, IIRC). >> >> Here was the patch: >> >> 2013-09-26 Barton E. Schaefer >> >> * 31770: Src/hist.c: memmove() instead of memcpy() for overlapping >> regions. >> >> I've re-checked Src/hist.c and there are no other cases where memcpy() is >> being used except with a newly-allocated buffer as the destination (so, no >> overlapping regions). >> >> } >> When I previously encountered the bug, I believe only the lookup from >> } >> history was garbled, i.e. the contents of .zsh_history were fine. >> } >> I'll have to confirm this on a different system though. >> >> Are you sharing history via a network-mounted home directory from >> multiple hosts? > The home directories are on local drives only. > I don't share history between computers at all. >>[...] > Originally, on the x86_64 machine, I was running zsh 5.0.3 from the > Ubuntu Package, > but per your suggestion I compiled 5.0.7 from source last month. The bug > persisted until > Mikael suggested setting "nohistreduceblanks" i.e. disabling > "histreduceblanks" > > Since then I've not encountered the bug anymore or at least the bug has > become so seldom > I've not encountered it yet again within the last month. Previously It > appeared about once in a day of work on the shell. Are you totally sure there were no more 5.0.3 instances running at that time? Or are you saying it works with histreduceblanks enabled again? -- Mikael Magnusson