I'm having trouble with the Subversion bundle, and I can't seem to get the Rails bundle to load.
Subversion commands always respond that my file is not a 'working copy'. Executing the identical command using svn works fine. I've set (correctly) the TM_SVN shell variable in the preferences.
The Rails bundle is located in ~/Library/Application Support/TextMate/Bundles/, right next to the Subversion bundle, which does load. I checked the Rails bundle out using svn co.
Any ideas?
Best, Eric
On Wed, 9 Mar 15:53 (-0800), Eric Ocean wrote:
Subversion commands always respond that my file is not a 'working copy'. Executing the identical command using svn works fine. I've set (correctly) the TM_SVN shell variable in the preferences.
Normally it should say this only if its so. Does all commands fail or do some work? You are using the newest beta and SVN commands, right? Maybe you can explain a bit more detailed on what filename and what conditions it fails because AFAIK it should work and I never got this error in wrong situations. If you are using the commands in a project, verify that you don't have wrong files selected in the drawer which could cause this error because some commands prefer a selection over the current file.
The Rails bundle is located in ~/Library/Application Support/TextMate/Bundles/, right next to the Subversion bundle, which does load. I checked the Rails bundle out using svn co.
Any ideas?
If you want Rails syntax you also need to check out the normal Ruby bundle because the Rails syntax depends on the Ruby syntax. If you have a revision from before 2005mar08 you should update because there where some changes in the last days. Maybe it works then.
Another problem could be that you still have older bundles in TextMate.app/Contents/SharedSupport/ which cause the problems with the rails bundle, I for myself deleted all bundles there and just have everything in my Application Support folder
On Mar 9, 2005, at 5:55 PM, Torsten Becker wrote:
On Wed, 9 Mar 15:53 (-0800), Eric Ocean wrote:
Subversion commands always respond that my file is not a 'working copy'. Executing the identical command using svn works fine. I've set (correctly) the TM_SVN shell variable in the preferences.
Normally it should say this only if its so. Does all commands fail or do some work? You are using the newest beta and SVN commands, right?
I believe so: 1.1b5 and I just checked out the latest Subversion, Ruby, and Rails bundles. I also deleted everything from the TextMate package in SharedSupport.
Some commands work, such as status and info. Add to repository fails. On the previous rev, it failed saying it couldn't find the working copy. You can see the error here: http://www.ampede.com/textmate/error.png . Here's the identical request in svn: http://www.ampede.com/textmate/success.png
Now, Add to Repository fails with:
/bin/bash: line 11: ruby: command not found
I have TM_RUBY set correctly. I can also run ruby just fine from the default bash shell.
If you want Rails syntax you also need to check out the normal Ruby bundle because the Rails syntax depends on the Ruby syntax. If you have a revision from before 2005mar08 you should update because there where some changes in the last days. Maybe it works then.
Is it just syntax? I guess I expected some snippets or commands. Maybe it's already working?
Another problem could be that you still have older bundles in TextMate.app/Contents/SharedSupport/ which cause the problems with the rails bundle, I for myself deleted all bundles there and just have everything in my Application Support folder
Thanks for the tip.
Best, Eric
-
Eric Ocean -
Torsten Becker