Hi,
I want to do Subversion checkout for the bundles but I have some cutsom setups in HTML and Markdown bundles. I have moved the newly created entries to the bundle named Ivan. Am I right to assume this only way to avoid SVN bundle checkout overwriting your setup?
Or any bundles in ~/Library/Application Support/TextMate will overrule the ones in /Library/Application Support/Textmate. What is the precedence for the location of the bundles? In other words, which bundles will TextMate use if the there are multiple copies exists in different locations?
From the Wiki page, I got the impression this is the order:
~/Library/Application Support/TextMate/ TextMate.app/Content/SharedSupport/ /Library/Application Support/TextMate/
Ivan
~/Library/Application Support/TextMate/ TextMate.app/Content/SharedSupport/ /Library/Application Support/TextMate/
For just about any OSX application it will look inside the application first, then the root Library, then the user level Library. Each one overrides the previous one. To have a custom bundle just change an item in it; they will be placed in your local Library by TextMate. It will never save anything to /Library. As for making a custom bundle that's fine... but I'm not sure of the precedence on that. Only the same names override each other, in another bundle they would both remain active and Allan will have to say which would win...
On 29/08/2005, at 0.21, Michael Sheets wrote:
~/Library/Application Support/TextMate/ TextMate.app/Content/SharedSupport/ /Library/Application Support/TextMate/
For just about any OSX application it will look inside the application first, then the root Library, then the user level Library.
Other way around, first it looks in personal library, and stuff there takes precedence over the global library which takes precedence over the application provided.
As for multiple copies of the same bundle, I am not sure on what level TextMate merges stuff (if it does; I think it doesn't, currently).
-- Sune.
On 29/08/2005, at 0.56, Sune Foldager wrote:
As for multiple copies of the same bundle, I am not sure on what level TextMate merges stuff (if it does; I think it doesn't, currently).
Each bundle has a UUID (universal unique identifier) in it's info.plist.
Each bundle item likewise has a UUID.
TextMate considers all bundles with the same UUID as being the same bundle (so if you rename e.g. the HTML bundle, it still gets merged with the default HTML bundle).
Bundles are merged on a item-by-item basis, using the UUID (not the name).
So if you change one item in a default bundle, only that single item ends up in ~/Library/... -- and it doesn't matter if you rename it, it will always hide the default item (duplicating it will make a copy with a new UUID, i.e. which doesn't override any default stuff).
On 28-08-2005 21:24, Ivan wrote:
I want to do Subversion checkout for the bundles but I have some cutsom setups in HTML and Markdown bundles. I have moved the newly created entries to the bundle named Ivan. Am I right to assume this only way to avoid SVN bundle checkout overwriting your setup?
I'm not completely sure what happens on initial checkout, I don't think it will overwrite anything. But after you have checked it out once, then your (local) changes will never get written over by subversion. It will do its best to merge it with the updates that happen in the repository and sometimes it can't and you have to do a manual merge (flagged by the letter 'C' when updated, or do 'svn status' in the local checkout directory).
Jeroen.
On 29/08/2005, at 8.37, Jeroen van der Ham wrote:
I want to do Subversion checkout for the bundles [...]
I'm not completely sure what happens on initial checkout, I don't think it will overwrite anything. But after you have checked it out once, then your (local) changes will never get written over by subversion. It will do its best to merge it with the updates that happen in the repository [...]
That's assuming you do the checkout in ~/Library -- users who are not going to checkin changes to the repository should always do the checkout in /Library to avoid this.