Hans,
Yes, we don't want to hide STDERR from perlmate. The main idea is to simply format the die message as a link so that you can travel back to the file quickly. The only thing we want to filter from STDERR are unhandled die's which we format ourselves. Everything else should be left alone. If extra formatting is required, we can do it using filter_stderr/filter_stdout.
- Alex
On Dec 1, 2006, at 8:17 AM, Hans-Joerg Bibiko wrote:
Hi,
there is still a problem with STDERR.
Some packages write messages directly to STDERR. So, to hide stderr in perlmate.rb makes problems.
Example:
#!/usr/bin/perl -w
use Foundation;
$f= NSString->foo("H");
STDERR: **** ERROR **** PerlObjCBridge: sendObjcMessage: Can't get NSMethodSignature for message "foo" Undefined subroutine &__PACKAGE__::die called at /System/Library/ Perl/Extras/5.8.6/darwin-thread-multi-2level/PerlObjCBridge.pm line 230.
But my latest exception_handler.pm only gets the info:
System Error: Undefined subroutine &__PACKAGE__::die called
in PerlObjCBridge.pm at line 230.*** ERROR **** PerlObjCBridge: ... is written to STDERR
So my question still is how to redirect this avoiding to modify scriptmate.rb???
Any hints ;)
-Hans
ps I already solved the problem to 'htmlize' the error messages.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate