On Oct 30, 2006, at 5:23 PM, Bill Bumgarner wrote:
Any chance this can wander into the subversion repository? I have a need for something exactly like this and the motivation to submit patches.
I think i will put in SVN once I get the first working release out :).
Also -- I grabbed the DMG and dropped the tmbundle/tmplugin into the right spots and:
/Volumes/Data/Users/bbum/Library/Application Support/TextMate/ Bundles/TerminalMate.tmbundle/Support/lib/terminal_mate.rb:7:in `initialize': No such file or directory - /Volumes/Data/Users/bbum/ Library/Application Support/TerminalMate/server.bin (Errno::ENOENT) from /Volumes/Data/Users/bbum/Library/Application Support/TextMate/ Bundles/TerminalMate.tmbundle/Support/lib/terminal_mate.rb:7:in `open' from /Volumes/Data/Users/bbum/Library/Application Support/TextMate/ Bundles/TerminalMate.tmbundle/Support/lib/terminal_mate.rb:7:in `initialize' from /tmp/temp_textmate.Ys206J:4:in `new' from /tmp/temp_textmate.Ys206J:4
The error is from missing Growl.framework (it's actually there, but has the incorrect path to the shared library). The problem is, I don't think you can have a layout like: `iTerm.framework/Versions/A/ Frameworks/Growl.framework` where `otool -L iTerm.framework/Versions/ A/iTerm` is
… @loader_path/Frameworks/Growl.framework/Versions/A/Growl …
I tried this, and it did not work. It is complicated to setup, however, so I may have made an error.
Solutions:
1. Include a script the user must run after installation. The script would run install_name_tool and change the shared library path of the iTerm framework linked against the Growl.framework to an absolute path. This solution requires the user have the Apple Developer Tools installed.
2. Have Allan include Growl.framework with TextMate, and just use `@exectuable_path` like normal. We would also include the Python/Perl/ Ruby extensions so you actually could use Growl from some of the bundles. I'm not sure how useful that would be, but it could be interesting for longer running commands.
-- Daniel