bugGNU Octave - Bugs: bug #55329, history_timestamp_format_string is...

 
 

bug #55329: history_timestamp_format_string is not initialized anymore

Submitter:  Markus Mützel <mmuetzel>
Submitted:  Sun 30 Dec 2018 10:32:54 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Regression
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 5.0.0 Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 07 Jan 2019 09:30:28 PM UTC, comment #6: 
Mike Miller <mtmiller>
Group Member
Sun 30 Dec 2018 09:24:39 PM UTC, comment #5: 

Using 'hg log libinterp/corefcn/oct-hist.cc' the only changeset hitting this file after the 4.4.1 release was this


changeset:   25994:f881d3e271d2
user:        John W. Eaton <jwe@octave.org>
date:        Wed Oct 31 19:32:41 2018 -0400
summary:     eliminate global and file-scope static variables in oct-hist.cc


Adding jwe to the CC list.

Rik <rik5>
Group administrator
Sun 30 Dec 2018 07:49:45 PM UTC, comment #4: 

Confirmed here as well.

Mike Miller <mtmiller>
Group Member
Sun 30 Dec 2018 06:12:52 PM UTC, comment #3: 

Is empty in 5.0.0 and dev (6.0.0).
FWIW, on my Linux box the latest cmd history time stamp for 5.0.0 is from Nov. 7.

Philip Nienhuis <philipnienhuis>
Group Member
Sun 30 Dec 2018 04:43:18 PM UTC, comment #2: 

Comment #2 got stripped...


history_timestamp_format_string


have any content on your system in 5.0.0 or dev?  On my system in 5.0.0 it is empty, thus might not be initialized correctly.

In 4.4.1 it has a value similar to that one you reported.

Kai Torben Ohlhus <siko1056>
Group Member
Sun 30 Dec 2018 04:40:23 PM UTC, comment #1: 

Confirmed for Linux (openSUSE 15.0) with Octave 5.0.0.


 __octave_config_info__ ("hg_id")
ans = f6cf96b71081


The issues might be related to the changes from cset
https://hg.savannah.gnu.org/hgweb/octave/rev/f881d3e271d2

Does the variable


history_timestamp_format_string
+verbatim-

have any content in your case?  On my system it is empty, thus might not be initialized correctly.  In Octave 4.4.1 it was filled with the string similar to that one you reported.

Kai Torben Ohlhus <siko1056>
Group Member
Sun 30 Dec 2018 10:32:54 AM UTC, original submission:  

In previous versions of Octave, lines similar to the following were added to the command history each time I started the GUI:

# Octave 4.4.1, Sat Dec 29 14:47:53 2018 GMT <unknown@ASUS-UX510UX>


These lines no longer appear in the current default branch (and probably the stable branch, too).
Have they been removed intentionally? I personally quite liked these "dividers" as an indication when I started a new Octave session.


Markus Mützel <mmuetzel>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by rik5
  • -email is unavailable- added by siko1056 (Posted a comment)
  • -email is unavailable- added by mmuetzel (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-01-07 mtmiller StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2018-12-30 rik5 Carbon-Copy- Added jwe
    2018-12-30 mtmiller CategoryGUI Interpreter
        SummaryNo more &quot;session dividers&quot; in command history history_timestamp_format_string is not initialized anymore
    2018-12-30 siko1056 Item GroupOther Regression
        StatusNone Confirmed

    Back to the top

    Powered by Savane 3.13-cf05.
    Corresponding source code