[Octave-bug-tracker] [bug #57027] command "history_file" does not work properly

[Hartmut]

URL:
  <https://savannah.gnu.org/bugs/?57027>

                 Summary: command "history_file" does not work properly
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Wed 09 Oct 2019 08:10:57 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: Any

    _______________________________________________________

Details:

I tried to use the Octave command "history_file()" for what I think it's ment
for, but it doesn't work properly.

Here is a way to reproduce it:
* change your .octaverc or startup.m file such that it contains the following
line of code: "history_file('~/test/.octave_hist');"
* delete the already existing history file ".octave_hist" in your home folder
(and maybe all other existing .octave_hist file in your system).
* start Octave
* type some commands into Octave, e.g. "123+456" and execute them
* close Octave again
* look into the folder "test", it will now have the history file
".octave_hist" that properly contains your freshly typed commands. So far, so
good.
* now restart Octave
* look at the history (it will be empty), or type the "arrow up" key in the
command window (nothing will show up)

I have observed this behavior with Octave 5.1 release, under Win10 as well as
under (Ubuntu) linux. Since I assume that this command "history_file()" used
to work properly at some time ago (the descsribed use case is the only one
this Octave command seems to have) I classified this bug report as
"regression".

(Maybe there is only the "append" option missing in this case of a
non-standard file location of the Octave history file?)




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57027>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/