Re^4: [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016

> works well within emacs.

To be fair, Komodo's debugger integration is better.

You can click on a line in the source code to add a break-point ... and IIRC (?) the next run will be automatically executed under the debugger then.

This could be implemented in Emacs of course and I haven't tried out alternative packages yet.

Simply because debugger is very low on my priority list.

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

Je suis Charlie!}

Comment on Re^4: [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016

Replies are listed 'Best First'.
Re^5: [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016 by doom (Deacon) on Jul 20, 2016 at 18:49 UTC
And if we're going to continue being fair, using perldb inside emacs isn't so good with apache, becuase you need to run in single-process mode. If you've got some subtle problem with multiple apache processes, you're better off using it with the Tk front-end. Setting breakpoints by clicking on a line sounds like an okay feature... I guess I might also like some sort of highlighting feature to see where breakpoints are set. Nevertheless, I highly recommend using perl -d with some sort of front-end that shows the context of the code you're looking at so you don't have to keep punching the "v" command (I think it's "v"... used to be "w" for window, but now that's watchexpression).	[reply]

Replies are listed 'Best First'.

Re^5: [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016
by doom (Deacon) on Jul 20, 2016 at 18:49 UTC

And if we're going to continue being fair, using perldb inside emacs isn't so good with apache, becuase you need to run in single-process mode. If you've got some subtle problem with multiple apache processes, you're better off using it with the Tk front-end.

Setting breakpoints by clicking on a line sounds like an okay feature... I guess I might also like some sort of highlighting feature to see where breakpoints are set.

Nevertheless, I highly recommend using perl -d with *some* sort of front-end that shows the context of the code you're looking at so you don't have to keep punching the "v" command (I think it's "v"... used to be "w" for window, but now that's watchexpression).

[reply]