comment on

I'm very used to tweak the perl-debugger for my needs to get a shell experience.

Under Win it's not that easy anymore because of the lack of CTRL shortcuts.

I can get used to the fact that CMD translates CTRL-a to select-all instead of beginning-of-line ...

... but CTRL-r for reverse searching the history is a life saver!

  DB<1> 

(reverse-i-search)`':
[download]

Now I tried calling the debugger under Git-Bash, which has a decent xterm emulation under bash. Unless when I call perl -de0 this is lost.

I also tried to install Term::ReadLine::Perl and Term::ReadLine::Zoid and did set %PERL_RL% accordingly.

I also tried installing Devel::REPL (incl. dependencies) and Reply but no luck with reverse search.

My best bet ATM is to run the debugger under emacs.

so ... what do you use and does it work the same under Win and Linux?

My requirements:

Nice-to-Have

This seems to be all available for Linux, but poorly tested resp. hard to achieve under Win.

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

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

°) !!dir in the debugger returns escape codes which "destroy" the terminal

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks