|
From: Daniel J S. <dan...@ie...> - 2013-11-19 07:11:49
|
On 11/18/2013 02:58 PM, pl...@pi... wrote: > Hi, > > is there was way to stop gnuplot compacting history? Do you mean that the current command is not repeated in history if it matches the previous most recent command in the history buffer? My history looks pretty lengthy, but I do seem to recall a limit. Also, given it isn't recent history I can't look through it and conclude that it is complete. > While I realise this is done to save storage space somewhere, this is a > constant annoyance. > > I have an annoying problem where something keeps changing and I need to > track exactly what is happening. > > In a shell I would use the history command to see _exactly_ what I did > and in what order to see what I have changed. I can see a true record of > my commands and repeat various parts of it until I reproduce and > understand the error. > > with gnuplot this does not seem possible because history is forever > being revised and compacted and no longer retains a useful record. In > fact "history" does not provide the command history. It's more like > recent favourites, that often saves some typing but it is not the > command history. > > I'm not that tight for space that I need to economise a few K. I'd much > rather save the few hours it's going to take me to find this problem > without a proper record of the commands I've issued to make the problem > repeatable. > > Is there a means of preventing gnuplot from compacting the command > history be removing dupes? I recall some years ago writing a history patch that allowed it to be configured in a couple ways: one being complete history, one being more condensed. I might still have that around if you are interested, but I'd have to search for it and I'm sure it has conflicting hunks by now. Dan |