On 3. May 2007, at 16:37, Gerd Knops wrote:
You know, I still haven't forgiven you for removing that output
option where one could enter a pattern. Since then my tools spend a
lot more code on formatting output then on getting their job done.
Here’s an idea: write your own tool and use that:
«my command»|«my tool that catches output»
You could do that tool in a dozen lines of perl and use tm_dialog to
open the output console. Within a few hours, you should have
something vastly superior to that crappy window I killed.
And now you want me to replace NSLog(@"I am
with something that opens some stupid file handle, then has to
write (to get a line break) something like NSLog(@"<ihateallan>I am
here</ihateallan>")? I hope you are kidding!
No, I wanted to enable programs to optionally do richer error
reporting (during development). Look at the runners we have for
AppleScript, Ruby, Python, etc. and how they present errors to the
user. This looks much better than a simple “some_file.cc:
85:5:Warning: bla bla bla”.