Re: Term::ReadLine and line-editing


P is for Practical
	PerlMonks

Re: Term::ReadLine and line-editing

by Discipulus (Canon)

on May 06, 2022 at 08:06 UTC ( [id://11143615]=note: print w/replies, xml )

Need Help??

in reply to Term::ReadLine and line-editing

Hello ibm1620,

from what I understand you should use Term::ReadLine as frontend, not directly Term::ReadLine::Gnu or ::Perl you can control with the env var PERL_RL which one is loaded. This is the standard way.

That said you can find interesting easy-osx-termreadlinegnu and this SO post but basically they both say to:

brew install readline

brew link --force readline

cpanm Term::ReadLine::Gnu

brew unlink readline
[download]

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re: Term::ReadLine and line-editing Select or Download Code

Replies are listed 'Best First'.

Re^2: Term::ReadLine and line-editing
by ibm1620 (Hermit) on May 06, 2022 at 12:30 UTC

I know about PERL_RL, my problem is that ::Perl creates visual blemishes in my prompt, and that installing ::Gnu is so complicated on a Mac that doesn't have developer tools. Although I'd gone ahead and had my client install Xcode COmmand Line Tools as prerequesite to installing perlbrew, simply to create a local Perl environment in which to install a readline module, it turned out that cpanm Term::ReadLine::Gnu would require homebrew in order to install readline-gnu, at which point I decided (with a little exasperation) to try installing ::Perl instead.

I'm still waiting to hear back about whether kcott's suggestion above (make'ing ::Gnu manually) worked for my client. Unfortunately my two Macs both have Xcode and homebrew so I can't test.

I hope I haven't muddied the waters further! :-)

[reply]
[d/l]

In Section Seekers of Perl Wisdom