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

Re: reading/saving history file dependent on isset(RCS)

X-seq: zsh-workers 29830
From: "Benjamin R. Haskell" <zsh@xxxxxxxxxx>
To: Greg Klanderman <gak@xxxxxxxxxxxxxx>
Subject: Re: reading/saving history file dependent on isset(RCS)
Date: Wed, 19 Oct 2011 14:48:27 -0400 (EDT)
Cc: Zsh list <zsh-workers@xxxxxxx>
In-reply-to: <20127.6190.501587.50858@gargle.gargle.HOWL>
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: <20127.6190.501587.50858@gargle.gargle.HOWL>

On Wed, 19 Oct 2011, Greg Klanderman wrote:

Hi, can someone explain the thinking behind reading and saving of thehistory 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 similarlyconditioned on that option.

This bit me last time I was trying to debug someone's history-relatedissues. I found that passage, too, (eventually), which is why I didn'tcomplain then. I don't understand the rationale for the conditioning.I'd be interested in seeing this changed if there's not a good reasonfor its being conditioned by default.


--
Best,
Ben

Follow-Ups:
- Re: reading/saving history file dependent on isset(RCS)
  - From: Bart Schaefer

References:
- reading/saving history file dependent on isset(RCS)
  - From: Greg Klanderman

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