|
From: Ethan M. <merritt@u.washington.edu> - 2007-06-04 22:22:51
|
On Monday 04 June 2007 15:14, Daniel J Sebald wrote: > > I don't like it at all. > > > > If I want the history, then I want it to show all the > > commands I issued, in the order they were issued. The condensed > > form you show above would not let me determine from the history > > command what was the value of 'foo' when I made the most recent > > plot. It's one thing to remove a series of "replot; replot; replot..." > > commands, since nothing changes between them. But your example > > is hiding important changes. > > Well, it could be programmed that way [but what user keeps typing replot; replot > without making any changes in between? :-)]. Anyone who closes the plot window to do something else for a while? To get it back again, he types "replot". I do this all the time. > The "do not put redundant commands > in the history stack" as But your example has no redundant commands! You are erasing commands that had a real effect on the contents of my screen. > gnuplot currently behaves has the same problem you're > pointing out. Ah, so maybe that's the reason I always found history to be unreliable. I thought it was just an annoying bug that some of my commands seemed to disappear. I never figured out any rhyme or reason to it. I strongly request that the default history behaviour is to leave all my commands in place. I would consider this a bug-fix. -- Ethan A Merritt |