From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9214 invoked by alias); 10 Jan 2016 07:46:41 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 21140 Received: (qmail 19929 invoked from network); 10 Jan 2016 07:46:40 -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,FREEMAIL_FROM, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6mKf7bmRwqkeQbrmiUeGPLzXCUehhuy6PyiAQ4cUJdU=; b=DlY1ceu/4ydtDecvt2zHG4BgiHNd7xTDCRvH9XjOobDqr30KpeU7c5mittvdKrUosX 4nruDbqiKb1mB5EZEre37ZBeTMP+f3GnSSD61gZ3zjl4LTINg316vgvdS1chjT5Qy70V DvCHQTWtOuK1JC/gJHHmj6RYNEAEwGQ7yeyBJYINEDJXTxZoXhOyVsLHDL++y0dGD+7H LWd9VgNoVv9uZ4zeE2RQ+eTWFGZWzlbpaeTZlLKplbzbTovGXHbX8hjPgIVkQMU4O++/ +xa52qRs1cdloAuG8KeeVeLdZeOa01TGHdfyI5+oZ65EUaGkFJKUcXhfMEy7jET9B20m /4VA== X-Received: by 10.25.141.129 with SMTP id p123mr19909124lfd.65.1452411996813; Sat, 09 Jan 2016 23:46:36 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <160106204452.ZM11191@torch.brasslantern.com> References: <160106204452.ZM11191@torch.brasslantern.com> From: Sebastian Gniazdowski Date: Sun, 10 Jan 2016 08:46:17 +0100 Message-ID: Subject: Re: Somehow my prompt broke in 5.2 To: Bart Schaefer Cc: Zsh Users Content-Type: text/plain; charset=UTF-8 On 7 January 2016 at 05:44, Bart Schaefer wrote: > There is a bug in Functions/VCS_Info/VCS_INFO_nvcsformats in the 5.2 > release -- a local variable got declared at the wrong scope when the > function was updated. > > Delete line 7 ( local -a msgs ) from VCS_INFO_nvcsformats and you > should be good to go. If you have problems with WARN_CREATE_GLOBAL, > add that same line to Functions/VCS_Info/vcs_info instead. Would be cool if this could be somehow workarounded in .zshrc, so that one can have robust configuration that will work anywhere right after install. The same I thought about the modification of _history-complete-older you proposed. But doing what I write is probably not possible. One could at least add a warning to .zshrc that would somehow detect if modifications aren't in place for given zsh. Best regards, Sebastian Gniazdowski