Thanks for you suggestions:
use Term::ReadLine; my $pkg = Term::ReadLine->ReadLine(); print "Term::ReadLine->ReadLine() says \'$pkg\'\n"; my $pkg2 = $ENV{PERL_RL}; print "ENV(PERL_RL) says \'$pkg2\'\n"; print "\@Term::ReadLine::ISA says ", @Term::ReadLine::ISA, "\n";
gives:

$ perl ../Tools/term_check.pl
Term::ReadLine->ReadLine() says 'Term::ReadLine::Gnu'
ENV(PERL_RL) says ''
@Term::ReadLine::ISA says Term::ReadLine::GnuTerm::ReadLine::Stub

So, as far as I can tell, I am running the Gnu version.

In reply to Re^2: term::readline::gnu extra spaces on completion by daverowntree
in thread term::readline::gnu extra spaces on completion by daverowntree

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.