From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29840-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9538 invoked by alias); 21 Oct 2011 12:41:04 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29840
Received: (qmail 13215 invoked from network); 21 Oct 2011 12:41:02 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <111021054029.ZM15446@torch.brasslantern.com>
Date: Fri, 21 Oct 2011 05:40:29 -0700
In-reply-to: <m3botb8uxb.fsf@klanderman.net>
Comments: In reply to Greg Klanderman <gak@klanderman.net>
 "Re: reading/saving history file dependent on isset(RCS)" (Oct 20, 12:55pm)
References: <20127.6190.501587.50858@gargle.gargle.HOWL>
	<alpine.LNX.2.01.1110191444090.23569@hp.internal>
	<111020001018.ZM9637@torch.brasslantern.com>	<m3botb8uxb.fsf@klanderman.net>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: reading/saving history file dependent on isset(RCS)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Oct 20, 12:55pm, Greg Klanderman wrote:
} 
} Based on there being no default setting for HISTFILE, can the
} isset(RCS) check can be safely removed for the readhistfile() call?

Something you said tripped a synapse.

No, this can't be safely removed.

I now seem to recall that this was added when sourcing /etc/zshenv was
exempted from NO_RCS.  If the system zshenv sets HISTFILE or SAVEHIST,
then you can get bad side-effects even with "zsh -f" unless NO_RCS
suppresses history file management.