[asterisk-bugs] [Asterisk 0016858]: [patch] asterisk command history loads as unusable garbage

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16858 
====================================================================== 
Reported By:                jw-asterisk
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16858
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.2 
JIRA:                       SWP-932 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-02-17 21:19 CST
Last Modified:              2010-03-05 10:19 CST
====================================================================== 
Summary:                    [patch] asterisk command history loads as unusable
garbage
Description: 
When using asterisk interactively with command interface a history file is
created (~/.asterisk_history). Lines written to the history file are
white-space encoded (in ast_el_write_history:history:case
H_SAVE:history_save:strvis).

But when the history file is loaded it reverse (strunvis) is not
performed.  Therefore the history becomes unusable garbage.
====================================================================== 

---------------------------------------------------------------------- 
 (0119027) jsmith (administrator) - 2010-03-05 10:19
 https://issues.asterisk.org/view.php?id=16858#c119027 
---------------------------------------------------------------------- 
By way of clarification, let me add a couple of points:

In the short term, the easiest way to solve the reported problem is to
have Fedora include a patch (similar to the one you suggested) along with
their patch set, as it's their patch that's triggering the behavior.

In the long term, steps 1 and 2 and 3 in the note above by seanbright will
be done, but because they're larger in scope, they're being considered as
"feature requests" and not as bugs.  That means they won't be applied to
release branches (such as 1.6.2), but will make it into the next release
branch after the work has been completed.

Make sense? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-05 10:19 jsmith         Note Added: 0119027                          
======================================================================