[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-04 07:49 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0118948) jw-asterisk (reporter) - 2010-03-04 07:49
 https://issues.asterisk.org/view.php?id=16858#c118948 
---------------------------------------------------------------------- 
My system is probably correctly configured and yours not.

That is because the xpg_echo setting performs correctly. With it off I get
the correct result - it echoes as \040. It would appear that your system is
misconfigured because it always incorrectly translates the \040 characters
as a space.

Also, on my system there is a difference between the action of "echo" and
"echo -e".

It really is up to you to find out what is wrong with your system.  It
isn't up to me.  My system is correct.  Yours is misconfigured.  The
evidence is in, and has demonstrated clearly that your system is flawed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-04 07:49 jw-asterisk    Note Added: 0118948                          
======================================================================