Description of problem:
After launching the new octave, from terminal, the history
seems not to be "enabled", i.e. there is no history.
Version-Release number of selected component (if applicable):
At the moment, it seems very often, but somehow
not always, once it happen the history was updated
(don't know if something special happened).
Steps to Reproduce:
Upgrade from 2.1.72-3 to 2.1.73-1 (maybe important).
Type some commands, like "ls", "plot(1:10)"...
History back, with arrow-up or "history" command.
The new commands are not browsed, only the one from the previous
session (eventually from 2.1.72) are available and "history"
does not return, of course, nothing new.
The immediate history should be browsable and available.
More funny is the following, if the ~/.octave_hist file is empty
(> ~/.octave_hist), or not present (rm ~/.octave_hist), the "history"
command produces a nice segmentation fault.
In 2.1.72 this was not happening, since "history" returned:
So, the history is always not empty.
I was partially able to duplicate this. I am still not sure what was causing it,
but the problem appears to be somehow related to the incompatibility of
octave-2.1.73-1 and octave-forge-2006.03.17-1 (see bug 186966). Only with both
of these installed simulaneously could I duplicate the problem of not seeing
past commands with the up arrow. Removing octave-forge, or installing a
recompiled version of octave-forge seemed to make the problem go away. I was not
able to create a core dump.
I am marking this as an octave-forge bug, dependent on 186966, and I am closing
it assuming that the forthcoming release of octave-forge-2006.03.17-2 will make
the problem go away.