On Thursday November 22 2012 12:33:28 PM you wrote:
Show quoted text> FWIW, cygwin is basically unix (the win7 reference is
> in case there is some windows specific "feature" that
> is relevant for the cygwin build. In my experience these
> are often due to users adding extra checks for win32
> rather than trusting the existing perl config and compile
> info.
Yes I know what cygwin is, you forced me to upgrade my cygwin installation on
my $work laptop just to try this out :-P I had to Data::Dumper on the
filehandle to see the difference. Very weird, but probably related to
libreadline on Windows vs real Unix.
Show quoted text> I was very excited to see this module (and the fact that
> more generalized event loop handling had made its way
> into Term::ReadLine. I've had an implementation for the
> GLUT+readline support in the works for some time but
> could never figure out how to get it into the standard
> framework.
If you have more examples of usage that you want to share, I'll take any I can
get - even if it's just a link to another distribution.
Show quoted text> I'm planning to re-implement using the event_loop
> feature and should have some example code to add
> if it is of interest. I'm planning to implement a
> with_Prima as well since that is a nice-perl GUI
The primary role of this distribution is the ex directory (and notice its
special LICENSE). So I'd prefer a standalone ex/Prima.pl first ;-)
Show quoted text> toolkit. Thanks for the prompt response and making
> this feature more easily accessible to all.
And I don't entirely get the "integrate ReadLine in a graphical environment"
thing :-) It might have been that the Tk support was to allow the Perl
debugger to work with Tk apps, I'm not sure. In that case, I probably should
look at ways to patch the debugger to allow this to work :-)
Thanks for the feedback!