octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57843] history_timestamp_format_string can't


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #57843] history_timestamp_format_string can't be set to empty string
Date: Mon, 17 Feb 2020 19:16:02 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36

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

                 Summary: history_timestamp_format_string can't be set to
empty string
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 17 Feb 2020 04:16:01 PM PST
                Category: Octave Function
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Regression
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 5.2.0
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

In Octave 4.4.1, history_timestamp_format_string("") could be used to set an
empty timestamp string, and this would prevent the session marker from being
written to the history file at all. This was a useful feature for users who
don't care about having a marker to tell when one Octave session ended.

In Octave 5.1 and 5.2, the function raises an error if an empty string is
passed as an argument.

A workaround is to pass a string that consists of a single space, but even
that is written as a blank line to the history file. The point is to bypass
writing the session marker at all.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]