[asterisk-bugs] [Asterisk 0016858]: 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:                     feedback
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:              
====================================================================== 
Date Submitted:             2010-02-17 21:19 CST
Last Modified:              2010-03-03 20:40 CST
====================================================================== 
Summary:                    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.
====================================================================== 

---------------------------------------------------------------------- 
 (0118937) jw-asterisk (reporter) - 2010-03-03 20:40
 https://issues.asterisk.org/view.php?id=16858#c118937 
---------------------------------------------------------------------- 
You should only ever get a single space output when you do "echo -e
'\040'".  That is why echo has a "-e" option.  If you are getting the
escape interpreted all of the time then you have another serious bug
elsewhere in your system (shell, glibc, tty driver, or whatever).

Hopefully in the future you will be more willing to look at the portion of
code that I clearly identified in my initial bug report, and properly
digest the supplied information, before leaping into denial mode.

Let he who is without sin cast the first stone. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-03 20:40 jw-asterisk    Note Added: 0118937                          
======================================================================