Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: VCS_INFO functions break with setopt no_unset

X-seq: zsh-workers 37422
From: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
To: Philip Sequeira <phsequei@xxxxxxxxx>
Subject: Re: VCS_INFO functions break with setopt no_unset
Date: Wed, 23 Dec 2015 02:38:25 +0100
Cc: zsh-workers@xxxxxxx
In-reply-to: <CAB_3nvqT89iskZ5wzQvUbMun7F80rsY4xJDmuiCp41=+baHomg@mail.gmail.com> (Philip Sequeira's message of "Mon, 7 Dec 2015 18:23:25 -0500")
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <CAB_3nvqT89iskZ5wzQvUbMun7F80rsY4xJDmuiCp41=+baHomg@mail.gmail.com>

Hi Philip,

Philip Sequeira wrote:
> With setopt no_unset in my config file, vcs_info fails with:
> VCS_INFO_maxexports:7: vcs: parameter not set

I just checked and this was not committed yet. So I am doing that now.

> The attached patch fixes it on my system, but I don't know if it's the
> best way to deal with the problem.

I always thought NO_UNSET was a rather weird setting; but I guess this
will do for now. If things get more complicated, we can always blast all
vcs_info functions with a stern "emulate -L zsh" on top of each
function.

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925

References:
- VCS_INFO functions break with setopt no_unset
  - From: Philip Sequeira

Messages sorted by: Reverse Date, Date, Thread, Author