From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27401 invoked by alias); 19 Oct 2011 18:49:00 -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: 29830 Received: (qmail 14568 invoked from network); 19 Oct 2011 18:48:58 -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 autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at benizi.com does not designate permitted sender hosts) Date: Wed, 19 Oct 2011 14:48:27 -0400 (EDT) From: "Benjamin R. Haskell" To: Greg Klanderman cc: Zsh list Subject: Re: reading/saving history file dependent on isset(RCS) In-Reply-To: <20127.6190.501587.50858@gargle.gargle.HOWL> Message-ID: References: <20127.6190.501587.50858@gargle.gargle.HOWL> User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 19 Oct 2011, Greg Klanderman wrote: > > Hi, can someone explain the thinking behind reading and saving of the > history file being dependent on isset(RCS)? The code predates CVS.. > Seems like if you've set HISTFILE/SAVEHIST, it should honor that. > > I did find this partially documented, in section "5.1 Startup/Shutdown Files": > > | Note also that the RCS option affects the saving of history files, > | i.e. if RCS is unset when the shell exits, no history file will be > | saved. > > but it does not document that reading the history file is similarly > conditioned on that option. This bit me last time I was trying to debug someone's history-related issues. I found that passage, too, (eventually), which is why I didn't complain then. I don't understand the rationale for the conditioning. I'd be interested in seeing this changed if there's not a good reason for its being conditioned by default. -- Best, Ben