On 22/6/2006, at 16:22, Dr. Drang wrote:

[...] I'd like to know the best way to resolve this difference. My guess is that the simplest way is to

1. throw away my current copies of /Applications/TextMate;

That one shouldn’t be necessary -- but it might be good to go to preferences -> software update and check for updates, to ensure it is “latest” if e.g. functionality you read about is not available/working.

2. throw away my current copies of Library/Application Support/

TextMate;

Yes, if you do not update the svn checkout you should NOT keep it around. It takes precedence over the built-in stuff. Btw: I assume there is a leading / to the path quoted.

3. install new TMs from a fresh download.

That would be only if you did step 1.

I do have certain snippets, macros, and commands of my own that I'd like to retain, so I would *not* throw away ~/Library/Application Support/TextMate. Does this procedure make sense?

Well, step 2 does. And yes, local stuff is in ~/Library, which is why I always recommend doing svn checkouts to /Library, i.e. to easier remove it again.

[...] When TM does a Software Update, do the new bundles go in / Applications/TextMate/Contents/SharedSupport/Bundles?

Yes -- a software update replaces TextMate.app, including the bundles within it.

If so, and if I'm going to use automatic Software Update instead of SVN, is there any need for /Library/Application Support/TextMate/ Bundles?

There is not, no. The only _need_ there is for svn checkouts is for bundles _not_ included with TextMate. In this case, I do recommend only doing a checkout of the actual bundle needed -- that way, the worst thing which can happen is, that this bundle becomes outdated.

I am however going to add a version file to the shared support folder and make TM use the one with the highest version, rather than the most local, as it seems the common answer to support questions these days is “svn up Support” or “rm -rf Support”.

On Jun 22, 2006, at 10:22 AM, Dr. Drang wrote:

I tried and failed to get the Blogging bundle working on either of my two computers yesterday. It's not the failures themselves, though, that's prompting my inquiry today, it's that the failures were different. Different behavior and different error messages.

I've had my own issues with keeping TM up to date. In my case, it was the Support folder lagging behind the bundles which caused the problem. I've been using a quick script to keep my bundles up to date, and I just added the ability to update the Support folder, too. I keep it in FastScripts' menu, though it's probably just as useful as a command in TM. Hopefully, unless I've missed something, it should now bring a TM install completely up to date, and I can stop emailing people when I break things.

I posted it online in case anyone else might find it useful: <http:// assortedgeekery.com/code/scriptmenu/textmate/update_bundles>.

-- Christopher Biagini http://assortedgeekery.com/ puevf.ovntvav@tznvy.pbz (Rot13 to descramble)

On Fri, Jun 23, 2006 at 04:02:45PM +0200, Allan Odgaard wrote:

On 23/6/2006, at 3:41, Christopher Biagini wrote:

...

[...] I posted it online in case anyone else might find it useful: http://assortedgeekery.com/code/scriptmenu/textmate/update_bundles.

This is pretty cool! Unfortunately running it on a full checkout is horribly slow, as apparently the startup/shutdown of svn takes 5-10 seconds, so there is a “5-10s x number of bundles” penalty for having the nice progress indicator.

(A little late here) I've posted a trivially-modified version of Christopher's script on the Wiki page linked above: this version does a simple `svn up` of the entire directory, increasing speed at the expense of the useful progress indicator.

Christopher, thanks for the script. Very handy.