|
From: Bastian M. <bma...@we...> - 2005-08-14 05:43:40
|
Ethan A Merritt wrote: > On Friday 12 August 2005 01:55 am, Petr Mikulik wrote: > >>I'm bit surprised what "unset historysize" is doing. It sets historysize >>to unlimited, not suppressing writing the history file. >> >>I propose the following changes: >>1. The code for history file is always compiled in (thus no need to >> --enable-history-file nor to modify dozen of files in config/). I am working on a patch to have gnuplot compiled with libedit from NETBSD. So could the #ifdef GNUPLOT_HISTORY statements be left in there? This would save us some very long #ifdefs ... >>2. By default, the history file is not read. It can be switched on in >> .gnuplot by "set historysize" How would the environment variable 'GNUPLOT_HISTORY_SIZE' fit in there? Could this be treated like "set historysize" in .gnuplot? >>3. Switching off writing/reading history file: "unset historysize" >>4. "set historysize -1" would set historysize to unlimited. > > > That all sounds reasonable. > > >>Ideas? > > > What does "set historysize 0" do? > Wouldn't is make sense to limit the size of 'in-memory' history to historysize as well? But that wouldn't work with your approach. So how about seperate commands for enabling/disabling saving of history? E.g. sth. like "set history on/off". Btw. the gnuplot readline code already does use historysize to limit the size of history in memory, whereas (as far is can tell) the GNU readline version does not. There it's only used for saving. Bastian |