On 2009-Mar-24, at 9:45 AM, Lucy Buykx wrote:

I then open up my project in TextMate and want to commit my code to the repository. It tells me that my code is not a working copy, so I say ok, lets checkout. Then it asks me for svn+ssh:// something so I type in the file path of the repository and a big error message thus...

If your repository is on your local system, you can use file: instead of svn+ssh:.

So in your case, you probably want to checkout file:///Users/lucy/Sites/wed2/Repository . I've never tried to checkout into an existing directory that already has files in it, etc. I'm not sure exactly what you've done so far or what you're wanting to accomplish, but I generally do something like this when moving an existing project into Subversion.

1. Create the repository with `svnadmin`. 2. Use `svn import` to commit the existing project directory to the repository. 3. Delete, rename, or move the project directory. 4. Use `svn checkout` to "recreate" the project directory as a working copy. 5. Open the new directory as a TextMate project.

Thanks for your notes Rob.

I have managed to get a working copy created and checked out. At least I think so. Using the TextMate Subversion bundle I tried to commit some file changes. No matter how I changed the files it always comes back with "nothing to commit, no modifications made".

Have been back and fine toothcombed the documentation on the TextMate website and come up with nothing more than "shift cmd A gets subversion menu up". Mind you the documentaiton for TextMate as a whole seems very thin to me so perhaps this is not unusual. Not your fault I know but I don't feel inclined to pay £50 for a software tool that isn't even documented.

Does anyone use the subversion bundle in TextMate to commit/checkout etc and can they point me to documentation that explains how to set it up and use it? Or do you all use TextMate for editing and handle Subversion stuff outside either command line or Versions or similar?

thanks

Rob McBroom wrote:

On 2009-Mar-24, at 9:45 AM, Lucy Buykx wrote:

...

I then open up my project in TextMate and want to commit my code to the repository. It tells me that my code is not a working copy, so I say ok, lets checkout. Then it asks me for svn+ssh:// something so I type in the file path of the repository and a big error message thus...

If your repository is on your local system, you can use file: instead of svn+ssh:.

So in your case, you probably want to checkout file:///Users/lucy/Sites/wed2/Repository . I've never tried to checkout into an existing directory that already has files in it, etc. I'm not sure exactly what you've done so far or what you're wanting to accomplish, but I generally do something like this when moving an existing project into Subversion.

1. Create the repository with `svnadmin`.
2. Use `svn import` to commit the existing project directory to the

repository. 3. Delete, rename, or move the project directory. 4. Use `svn checkout` to "recreate" the project directory as a working copy. 5. Open the new directory as a TextMate project.

Lucy,

Lucy Buykx schrieb:

Have been back and fine toothcombed the documentation on the TextMate website and come up with nothing more than "shift cmd A gets subversion menu up". Mind you the documentaiton for TextMate as a whole seems very thin to me so perhaps this is not unusual. Not your fault I know but I don't feel inclined to pay £50 for a software tool that isn't even documented.

so basically you are complaining that the documentation of a text editor doesn't explain you the basics of every language and tool it supports? Heh. Please don't look at the documentation of the Haskell and Erlang bundles. :)

Yes, lots of people here use the subversion bundle. In fact, I'd guess that it's around 80-90% of the people, and near 100% of the professional programmers. But the difference is that they know how SVN works, and probably they haven't learned it by complaining on a support mailing list for a text editor, but instead just read up about SVN, the tool they were trying to use.

But I don't want to be rude. Instead, I'll give you a link. Incidentally, it's the first link which comes up if you Google "svn" and "book".

http://svnbook.red-bean.com/en/1.4/

Once you have an idea of how Subversion works, you'll find that the Subversion bundle of Textmate works perfectly as documented, and is documented perfectly.

Now you can decide if you want to spend 48 € on the best text editor around, but please don't base your decision on your non-understanding of Subversion. It would be unfair to Alan, who has put a great deal of work into a great tool.

You're welcome. I'll be here all day. ;)

Thorsten

On 2009-03-27 17:23, Gerd Knops threw down some bits like this:

On Mar 27, 2009, at 3:45 PM, Thorsten Hamann wrote:

...

Yes, lots of people here use the subversion bundle. In fact, I'd guess that it's around 80-90% of the people, and near 100% of the professional programmers.

I can only shake my head when people throw out wild guesses like that...

Subversion is quickly being obsoleted by more powerful tools.

Gerd is right. Subversion is not that big. In corporations you're more likely to find something like Perforce or SourceSafe. Just because it's big in the open source realm doesn't mean it's big everywhere.

Dan

On Fri, Mar 27, 2009 at 6:40 PM, Dan Weeks <dan+textmate@danimal.orgdan%2Btextmate@danimal.org

wrote:

On 2009-03-27 17:23, Gerd Knops threw down some bits like this:

...

On Mar 27, 2009, at 3:45 PM, Thorsten Hamann wrote:

...

Yes, lots of people here use the subversion bundle. In fact, I'd guess that it's around 80-90% of the people, and near 100% of the professional programmers.

I can only shake my head when people throw out wild guesses like that...

Subversion is quickly being obsoleted by more powerful tools.

Gerd is right. Subversion is not that big. In corporations you're more likely to find something like Perforce or SourceSafe. Just because it's big in the open source realm doesn't mean it's big everywhere.

Not just the corporations are looking at alternatives to svn.

I don't have any numbers but..

From where I sit I'm amazed at the rapid adoption of git in the open source

community. While subversion might still be big, git has a lot of upward velocity.

A lot of this has to do, it seems to me, with the groundbreaking combination of social networking with version control as exemplified by sites like github.com.

On Fri, Mar 27, 2009 at 9:26 PM, Gerd Knops gerti-textmate@bitart.comwrote:

I expect git adaptation to continue growing rapidly. It wasn't quite usable for the masses 2 years ago, but it sure is now. And IMHO it is a lot nicer to use than most other systems out there. Lately a number of high-profile projects have switched to git (X.org and perl come to mind). You are right though about bigger companies, they will be slow to change.

I'd argue that the biggest reason for this is that the decisions on what tools to use in bigger companies are just as, if not more, likely to be made between executives and software salesmen on golf courses, than by developers in development labs.