Your SOPW is so close to incomprehensible (to me, OMMV, or incoherent) that I'm merely making a WAG as to your intent. But because the code below probably won't help much, please explain why you seem to be using Term::ReadLine to WRITE to a console. 1.

#!/usr/bin/perl
use strict;
use warnings;
use 5.018;
use Term::Readline;

my $term_out = "This is a test. This is being written from a terminal.
+ As I write, I get closer to the edge. \nThe prompt continues on the 
+line below without me hitting the return key.\n When I press up with 
+an arrow key, nothing untoward happens on W7 w/perl v 5.018.";

my $term = Term::ReadLine->new("APP DESCRIPTION");
my $OUT = $term->OUT|| *STDOUT; 
$term->addhistory(my $fake_line);
my $line = $term->readline("Strike RETURN to continue: ");
 
say $line . $term_out;

[download]

Note the use of strict and warnings.

1. Perhaps this fragment from Term::Readline's doc has sent you in the direction shown in your parent node.

 "new"       returns the handle for subsequent calls to following
             functions. Argument is the name of the application.
             Optionally can be followed by two arguments for "IN" and
             "OUT" filehandles. These arguments should be globs.

 "readline"  gets an input line, *possibly* with actual "readline"
             support. Trailing newline is removed. Returns "undef" on
             "EOF".

 "addhistory"
             adds the line to the history of input, from where it can 
+be
             used if the actual "readline" is present.

[download]

If so, please offer a (minimal) version of the full code which displays the same anomalies (control chars) you mentioned and a sample of the source text

<
If I've misconstrued your question or the logic needed to answer it, I offer my apologies to all those electrons which were inconvenienced by the creation of this post.

In reply to Re: Revising Input Method by ww
in thread Revising Input Method by PinePerl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.