comment on

> I was under the impression that it launches programs under debug by redirecting its STDIN and STDOUT to a "console" buffer

You are describing the debugger API via M-x perldb.

It runs the debugger in a terminal emulation in an extra buffer and is in parallel scrolling the current point in the original source buffer.

And it kind of works after typing c for continue (debugger command) I can input stuff. It actually looks exactly like when run with perl -d

Tho it doesn't seem to have auto linking of Perl's error messages.

I will update my OP later with an SSCCE explaining the output.

> I was under the impression that it launches programs under debug by redirecting its STDIN and STDOUT to a "console" buffer

Well I'm using mode-compile but emacs is more TIMTOWTDI than Perl. I think mode-compile was originally designed for make that's why interactive input isn't that important.

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

Wikisyntax for the Monastery}

In reply to Re^2: Prompting for input inside IDE run (was Reading from STDIN) by LanX
in thread Prompting for input inside IDE run (was Reading from STDIN) by LanX

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.


Do you know where your variables are?
	PerlMonks