thanks for all the efforts you guys put into this. These two solutions solved my issues as well. Thank you!
On 2010-02-11, at 1:00 PM, firstname.lastname@example.org wrote:
This is the same trace I get with the dylib *enabled*, which leads me to believe that you've still got a dylib somewhere. You can make sure it's disabled by setting the variable TM_INTERACTIVE_INPUT_DISABLED=true in TextMate's shell variables preference pane.
TextMate will always use the dylib at $TM_SUPPORT_PATH/lib/tm_interactive_input.dylib. You can find $TM_SUPPORT_PATH by entering ?echo $TM_SUPPORT_PATH? in a TextMate document and press CTRL+R to run that line with bash.
Thanks for all your suggestions. Both of these suggestions worked for me. Setting the environment variable seems to be the easiest solution. Also, your second suggestion allowed me to find a third (and final?) copy of the dylib in:
~/Library/Application Support/TextMate/Pristine Copy/Support/lib/
Thank you for your help and your patience. -Tony