Re: Best Perl REPL/Shell on Win (and Linux)?

I use Reply and is has pretty much everything on your requirements and nice-to-have lists, but no idea how well it performs on Windows. Have you tried Term::Readline::Gnu to get history, tab-completion, etc working? I don't know how well it works on Windows, but it's very good on Linux.

toby döt ink

Comment on Re: Best Perl REPL/Shell on Win (and Linux)?

Replies are listed 'Best First'.
Re^2: Best Perl REPL/Shell on Win (and Linux)? by LanX (Saint) on Jan 09, 2020 at 18:37 UTC
> Have you tried Term::Readline::Gnu ... That's not that easy (Please correct me someone if I get the terminology wrong.) The standard console window on Windows is cmd.exe while it's a term(inal) on Linux. They have very different terminal emulations that includes escape sequences to navigate and write the console. Term::ReadLine::Gnu and Term::ReadKey are XS module for such nix consoles. Now Git-Bash seems to be such a terminal, but comes with it's own bundled Perl and installing new modules there doesn't seem to be a good idea and fails anyway. Though it might be possible to run a different Perl installation there using Term::ReadLine::Perl (a non XS backend) But the cleanest solution would be a Term::ReadLine backend which translates to CMD consoles. > to get history, tab-completion, etc working?* most of it actually works, it's only the key-binding which is not triggering. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]

Replies are listed 'Best First'.

Re^2: Best Perl REPL/Shell on Win (and Linux)?
by LanX (Saint) on Jan 09, 2020 at 18:37 UTC

> Have you tried Term::Readline::Gnu ...

That's not that easy

(Please correct me someone if I get the terminology wrong.)

The standard console window on Windows is cmd.exe while it's a term(inal) on Linux.

They have very different terminal emulations that includes escape sequences to navigate and write the console.

Term::ReadLine::Gnu and Term::ReadKey are XS module for such *nix consoles.

Now Git-Bash seems to be such a terminal, but comes with it's own bundled Perl and installing new modules there doesn't seem to be a good idea and fails anyway.

Though it might be possible to run a different Perl installation there using Term::ReadLine::Perl (a non XS backend)

But the cleanest solution would be a Term::ReadLine backend which translates to CMD consoles.

> to get history, tab-completion, etc working?

most of it actually works, it's only the key-binding which is not triggering.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

[reply]