Cool, I will try that. Robert
"Martijn van Iersel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > If you use command subsystem 2, you get an interactive terminal. > However, then you can't catch possible compiler errors. For perl I use > the following properties, so it compiles first in the output panel and > then runs in a terminal: > > #the following changes the go command to "compile & run" perl scripts > #the & pause will close the terminal after pressing a key > command.go.$(file.patterns.perl)=cmd /C perl -w $(FileNameExt) & pause > command.go.subsystem.$(file.patterns.perl)=2 > command.go.needs.$(file.patterns.perl)=perl -c -w $(FileNameExt) > command.go.needs.subsystem.$(file.patterns.perl)=0 > > > Robert Hicks wrote: > > >Is it interactive? If I put in (I use Perl) and "chomp(my $answer = > ><STDIN>); will that allow me to type at the console? > > > >Robert > > > > > > > >_______________________________________________ > >Scite-interest mailing list > >[email protected] > >http://mailman.lyra.org/mailman/listinfo/scite-interest > > > > _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
