On 2014-04-01 16:53, Gerd Knops wrote:
I think a better approach for that would be if you could inject scopes into the
document (like set error scope on line 54, char 12). Then you can use styles as
usual to highlight the errors. Obviously it would also be necessary to be able
to attach metadata to those warning/error scopes.
I haven't started to think about how to a build script could communicate
with TextMate yet. I started with the visual.
Build systems are easiest ran in a script. So to get fast adoption of such a
feature, custom build scripts would need to be able to communicate with
TextMate. Maybe extend the txmt URL scheme? Like
Start a build (resets previous build scopes)
txmt://build/?type=init
Add a warning (adds a build scope, errors would work similar)
txmt://build/?type=warning&url=file:///Users/me/Projects/MyProject/MySourceFile.m&line=54&char=12&text=Method+not+found
End a build (Display some feedback in the UI)
txmt://build/?type=done&text=2+Errors++3+Warnings
I don't like this approach. Unless I misunderstand something the user
need to click on these links. I want this to be usable without a
separate output window.
--
/Jacob Carlborg
_______________________________________________
textmate-dev mailing list
textmate-dev@lists.macromates.com
http://lists.macromates.com/listinfo/textmate-dev
