Hi,
I am a TextMate 2 Alpha user since the day it was made public. However, some months ago an update of it shredded my TM1 installation because the support folder was then renamed from "Avian" to "TextMate". This was unfortunate but I could live with it since I only relied on TM1 for HTML zen coding anyway.
Once in a while I am trying out new bundles and I am noticing that if I want to install bundles manually I still have to do this in "Application Support/Avian/Pristine Copy/Bundles" since TextMate will ignore everything in "Application Support/TextMate/Bundles" or "Application Support/TextMate/Pristine Copy/Bundles".
Maybe there is a deeper sense to it I just don't get but I find this really confusing and thus hard to work with. Or maybe I am just getting it wrong and there is a command I need to run or a file I need to delete for this to work properly.
Any help or info regarding this is greatly appreciated.
Thanks, Torsten
On 2014-01-07 09:06, Torsten Walter wrote:
Hi,
I am a TextMate 2 Alpha user since the day it was made public. However, some months ago an update of it shredded my TM1 installation because the support folder was then renamed from "Avian" to "TextMate". This was unfortunate but I could live with it since I only relied on TM1 for HTML zen coding anyway.
Once in a while I am trying out new bundles and I am noticing that if I want to install bundles manually I still have to do this in "Application Support/Avian/Pristine Copy/Bundles" since TextMate will ignore everything in "Application Support/TextMate/Bundles" or "Application Support/TextMate/Pristine Copy/Bundles".
Maybe there is a deeper sense to it I just don't get but I find this really confusing and thus hard to work with. Or maybe I am just getting it wrong and there is a command I need to run or a file I need to delete for this to work properly.
Any help or info regarding this is greatly appreciated.
TextMate 1 and 2 uses different directories in Application Support to be able to co-exist.
It is reasonable that TextMate 2 has its own Avian folder for bundles. I think what Torsten is complaining about (and I agree) is that TextMate2 uses _two_ Application Support folders. It gets its custom bundles from the Avian folder, but it also invades TextMate 1's TextMate folder and puts some stuff in there. So it uses the TextMate folder, but, as Torsten rightly says, it ignores the custom bundles in the TextMate folder, because it is getting those from the Avian folder.
Torsten, if you don't want duplicate copies of the custom bundles, you can use symlinks in the Avian folder to point into the TextMate folder. m.
On Jan 7, 2014, at 1:40 AM, Jacob Carlborg doob@me.com wrote:
On 2014-01-07 09:06, Torsten Walter wrote:
Hi,
I am a TextMate 2 Alpha user since the day it was made public. However, some months ago an update of it shredded my TM1 installation because the support folder was then renamed from "Avian" to "TextMate". This was unfortunate but I could live with it since I only relied on TM1 for HTML zen coding anyway.
Once in a while I am trying out new bundles and I am noticing that if I want to install bundles manually I still have to do this in "Application Support/Avian/Pristine Copy/Bundles" since TextMate will ignore everything in "Application Support/TextMate/Bundles" or "Application Support/TextMate/Pristine Copy/Bundles".
Maybe there is a deeper sense to it I just don't get but I find this really confusing and thus hard to work with. Or maybe I am just getting it wrong and there is a command I need to run or a file I need to delete for this to work properly.
Any help or info regarding this is greatly appreciated.
TextMate 1 and 2 uses different directories in Application Support to be able to co-exist.
-- /Jacob Carlborg
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
On Jan 7, 2014, at 3:40 AM, Jacob Carlborg doob@me.com wrote:
TextMate 1 and 2 uses different directories in Application Support to be able to co-exist.
This is correct and it’s just a temporary solution, during the alpha we wanted to make sure you could run 1.x and 2.0 side-by-side. So 2.0 will store items that didn’t exist in 1.x in their final places within the TextMate folder while temporarily storing 2.0 items in the Avian folder to avoid conflicts. As we move closer to a final release we’ll move everything back to TextMate and get rid of the Avian directory.
On Jan 7, 2014, at 3:16 PM, Michael Sheets mummer@whitefalls.org wrote:
On Jan 7, 2014, at 3:40 AM, Jacob Carlborg doob@me.com wrote:
TextMate 1 and 2 uses different directories in Application Support to be able to co-exist.
This is correct and it’s just a temporary solution, during the alpha we wanted to make sure you could run 1.x and 2.0 side-by-side. So 2.0 will store items that didn’t exist in 1.x in their final places within the TextMate folder while temporarily storing 2.0 items in the Avian folder to avoid conflicts. As we move closer to a final release we’ll move everything back to TextMate and get rid of the Avian directory.
But that's the wrong answer. They need to continue to avoid conflicts. For example, the third-party AsciiDoc bundle is very broken under TextMate 2. I don't know why and I don't have much time (or ability) to figure it out. My solution is to run TextMate 1. But I sometimes look at the files under TextMate 2 and try to tweak a different copy of the bundle, to fix it. I need those changes not to affect the bundle used under TextMate 1. If the distinction between the TextMate 1 bundle and the TextMate 2 bundle suddenly goes away, that will be a disaster.
m.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
On 8 Jan 2014, at 7:50, Matt Neuburg wrote:
But that's the wrong answer. They need to continue to avoid conflicts. For example, the third-party AsciiDoc bundle is very broken under TextMate 2. I don't know why and I don't have much time (or ability) to figure it out […]
The goal is to be backwards compatible¹. So if the AsciiDoc bundle is broken with TextMate 2 then it sounds like there is an issue with TextMate 2.
Can you give an example of how it is broken?
¹ Except for template support and some minor things where we decided it would be best to break compatibility because 1.x was “wrong”.
On Jan 9, 2014, at 7:18 PM, Allan Odgaard mailinglist@textmate.org wrote:
On 8 Jan 2014, at 7:50, Matt Neuburg wrote:
But that's the wrong answer. They need to continue to avoid conflicts. For example, the third-party AsciiDoc bundle is very broken under TextMate 2. I don't know why and I don't have much time (or ability) to figure it out […]
The goal is to be backwards compatible¹. So if the AsciiDoc bundle is broken with TextMate 2 then it sounds like there is an issue with TextMate 2.
Can you give an example of how it is broken?
No, it's too complicated to explain. :) I *think* it has something to do with the way the AsciiDoc bundle is dependent on the Markdown bundle, which has greatly changed. I think I am going to have to rewrite the entire bundle from scratch, building it from the ground up. But this is going to take a long time, as I didn't write the original bundle, and writing bundles is complicated, and I've never done it before (and the documentation, especially for TextMate 2 bundles, is not all that it could be).
However, let's stick to the point. Of course you can do whatever you like, but I *beg* you to consider *not* ultimately merging TextMate 1 and TextMate 2 application support folders. The extent to which TextMate 2 uses TextMate 1's application support is _already_ somewhat disastrous for me. More important, people may have good reasons to keep using TextMate 1 side by side with TextMate 2, and to use different bundles in TextMate 1 than they use in TextMate 2.
Remember, I can always make them use the same bundle by using a symlink. But if you force-merge the two application support folders, then I can't separate them. m.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
-
Allan Odgaard -
Jacob Carlborg -
Matt Neuburg -
Michael Sheets -
Torsten Walter