I'd really like to have the results of "make" pop up in a Error
Results browser, so that I can easily navigate its issues and quickly
correct errors.

This thread 
http://groups.google.com/group/bbedit/browse_thread/thread/24ca184f74a13948/
discusses using a worksheet.  That doesn't save me much time.  I
really want a very fast "next error" and "previous error" keystroke
that gets me correcting things immediately.

Page 202 of the BBEdit User Manual (9.6) says: “When you use the HTML
syntax checker, link checker, or update tool, BBEdit will open an
error results browser to display any errors generated by the command.
BBEdit will also open an error results browser to list errors
generated by Perl scripts.” and it has a nice picture of just what I
want.

I can't find any documentation of how I might connect script output to
one of these browsers.  Presumably, BBEdit is running a script, then
parsing some output in order to feed it to the browser.  I tried
tricking BBEdit into thinking that make's errors were coming from
Perl, like this:


#!/usr/bin/perl -w
use strict;
open MAKE, "cd \$HOME/project/foo && make 2>&1 |";
while(<MAKE>) {
        if(/^(.*?):(\d+):\s*(.*)$/) {
                print STDERR "$3 at $1 line $2.\n";
        } else {
                print;
        }
}

but this didn't work.  BBEdit still sent all the output to a plain old
script results window.

This would really help my edit/compile/run cycle.  Xcode does it
nicely, except that I seem to crash Xcode every 10 minutes.  (Try
typing Japanese into its gdb window.)

-- 
You received this message because you are subscribed to the 
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem, 
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

Reply via email to