Hello everybody,
as nobody answered my question regarding "Configuring syntax highlighting programmatically", I suppose there is no easy/standard way to programmatically configure syntax highlighting. Therefore, I will try to modify the syntax highlighting file and the current theme file programmatically and then tell TextMate to reload them. While searching how to do this, I found OSX::PropertyList.load to read property lists and after asking google I also found that there is a function OSX::PropertyList.dump. However, finding this information was more or less fortune. Is there a central place where I can search for TextMate documentation for bundle developers? How was I supposed to find out about OSX::PropertyList.dump?
Best regards Daniel Sadilek
Hi,
saving the theme file works. But now I'm stuck with the next problem. Telling TextMate to reload the bundles with osascript -e 'tell app "TextMate" to reload bundles' does not cause it to reload the current theme. Even locating the theme file in Finder and double clicking it does not help. I have to restart TextMate :(. Is there any way to tell TextMate to reload the (current) theme.
Best regards Daniel Sadilek
Am 13.04.2008 um 17:26 schrieb Daniel Sadilek:
Hello everybody,
as nobody answered my question regarding "Configuring syntax highlighting programmatically", I suppose there is no easy/standard way to programmatically configure syntax highlighting. Therefore, I will try to modify the syntax highlighting file and the current theme file programmatically and then tell TextMate to reload them. While searching how to do this, I found OSX::PropertyList.load to read property lists and after asking google I also found that there is a function OSX::PropertyList.dump. However, finding this information was more or less fortune. Is there a central place where I can search for TextMate documentation for bundle developers? How was I supposed to find out about OSX::PropertyList.dump?
Best regards Daniel Sadilek
On 13 Apr 2008, at 10:46, Daniel Sadilek wrote:
Hi,
saving the theme file works. But now I'm stuck with the next problem. Telling TextMate to reload the bundles with osascript -e 'tell app "TextMate" to reload bundles' does not cause it to reload the current theme. Even locating the theme file in Finder and double clicking it does not help. I have to restart TextMate :(. Is there any way to tell TextMate to reload the (current) theme.
If you look at the Diff bundle, it includes Preference items with some foreground/background colour definitions, I would imagine this would be better suited to what you are doing (since reloading bundles should work fine then).
The plist extension has a readme…
/Library/Application Support/TextMate/Tools/plist/README
Hmm, I don't have a TextMate folder under "/Library/Application Support" and "~/Library/Application Support" does not contain such a file. Neither does the TextMate.app bundle. I use TextMate Version 1.5.7 (1436).
Daniel
On 15 Apr 2008, at 12:59, Daniel Sadilek wrote:
The plist extension has a readme…
/Library/Application Support/TextMate/Tools/plist/README
Hmm, I don't have a TextMate folder under "/Library/Application Support" and "~/Library/Application Support" does not contain such a file. Neither does the TextMate.app bundle. I use TextMate Version 1.5.7 (1436).
On 13 Apr 2008, at 17:26, Daniel Sadilek wrote:
as nobody answered my question regarding "Configuring syntax highlighting programmatically", I suppose there is no easy/standard way to programmatically configure syntax highlighting.
I answered it: http://lists.macromates.com/pipermail/textmate/2008-April/025034.html
[...] Is there a central place where I can search for TextMate documentation for bundle developers? How was I supposed to find out about OSX::PropertyList.dump?
Everything under TM_SUPPORT_PATH is at a public repository here: http://macromates.com/svn/Bundles/trunk/
While the documentation is sparse, there is “svn log” on the items. Much of the items are script which can easily be inspected and the binaries (like the plist ruby extension) have the source in the Tools folder.