TM2s HTML output window is somewhat limited compared to TM1:
- it uses sort of *tabs*, so I can't have multiple windows next to each other (handy to remove clutter and usually welcome, but when I run multiple apps/scripts in parallel I need separate windows to monitor them)
- it only allows one 'long running' process at a time
Since my projects often include multiple apps and/or scripts that interdepend and I need to run them side by side (eg client server etc). I used to use HTML output windows, so that I could have specially formatted log messages be clickable and get me to the correct location in the source code etc.
So I wrote an application that provides multiple HTML output windows and remembers their individual placement and size. It is called ApLo, and available as source here:
and wrapped into a TextMate bundle here:
For starters I wrote an Xcode4 bundle that goes with it:
As time permits I plan to add support for iOS projects as well, and STDOUT/STDERR parsers for other languages (perl, lua) as I come across them.
Maybe these bundles will be useful for others as well.
On Jan 23, 2012, at 1:04 AM, Gerd Knops firstname.lastname@example.org wrote:
[…] I wrote an application that provides multiple HTML output windows and remembers their individual placement and size. It is called ApLo […]
Have you considered bringing back something like TextMate 1.0’s simple output system where user supplied the pattern to match warnings/errors and then TextMate showed this in a list (I still remember you being upset when I removed this stuff ;) )?
Mainly what I want to achieve (this time) is having ⌘1-n to go to the n’th error/warning.
I do this all the time with Find in Folder, i.e. ⇧⌘F → enter text → ↩ → ⌘1 and boom! at the desired place in the source¹, and it feels very efficient and I miss this short when I see build errors, though the experience feels very close to doing searches, so much that I am thinking that the results view from Find in Folder could actually be re-used more or less as-is (speaking visually) for command output.
¹ I have a convention where I always call functions by following the name directly with the opening parenthesis, but when I declare it, it’s always separated by one space. This means if I want to go to the declaration of `some_function` I can simply search for `some_function ` and it’ll be found without the noise of all the calls to `some_function`. I believe this (and other) simple conventions are part of the reason why I never got into ctags.