On Friday 23 January 2009 14:21:08 Rafael Garcia-Suarez wrote:
> But: what would be *cool* would be a debug session in a custom irssi
> window.
> -!- Irssi: join to &perl5db was synced in 0 secs
> <@rgs> $x = 39+3;
> <@rgs> print $x;
> <perl> 42

/window new hide
/exec -interactive perl -d -e 0

But that doesn't echo your own commands into the window, so maybe something 
like /exec -interactive tee /dev/stderr | perl -d -e 0, but that doesn't seem 
to want to quit here without a kill.

Anyways, being able to actually debug irssi scripts would be nice...
Is this an irssi-specific problem? Is debugging Perl embedded into another 
program in a way similar as in irssi rather unexplored territory, or is it 
really supposed to work?
Perhaps it's because irssi (glib) controls the main loop and not Perl?



Reply via email to