Re: Term::Shell readline

debugging a Term::ReadLine application inside the debugger is very tricky, because it's also needing Term:ReadLine. That's like transporting a motor-scooter on a motor-scooter.°

I'm surprised you can do anything meaningful now, but if you say it "works", then this means the debugger is providing the right readline environment.

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}

°) well I've seen this in Vietnam but that's another story ...

Comment on Re: Term::Shell readline

Replies are listed 'Best First'.
Re^2: Term::Shell readline by cavac (Prior) on Mar 10, 2023 at 13:11 UTC
debugging a Term::ReadLine application inside the debugger is very tricky, because it's also needing Term:ReadLine. Would rebinding the application STDIN/STDOUT to some other terminal (or a unix domain socket) work? PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP	[reply]
Re^3: Term::Shell readline by LanX (Saint) on Mar 10, 2023 at 13:51 UTC
Yes. I think Discipulus and me had this discussion before. (I'll dig °) The debugger has by itself the possibility to communicate via a socket, that's how debugging is implemented inside emacs and other IDEs. Hence the easiest way should be to start the debugger inside an IDE and wrap the app inside it's own terminal. Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery} update °) Here: How to perldebug a Term::ReadLine application (sic ... added to my profile page now)	[reply]

update