So one of the things I did often in TM1 was create projects with files that are located all over the file system. Seems like projects in TM2 are based off of a single folder, but I admit I don't understand the .tm_properties stuff that well yet.
Is there a way to use .tm_properties to do what I did in TM1? If so, can someone post an example .tm_properties?
Thanks.
Is there a way to use .tm_properties to do what I did in TM1? If so, can someone post an example .tm_properties?
AFAIK .tm_properties is not really equivalent of TM1 projects, but it is more like customization of TM2 settings that is being applied only on the files that lay within the folder where .tm_properties is placed. So it is more like equivalent of GIT's .gitconfig, see:
http://blog.macromates.com/2011/git-style-configuration/
Also I recommend browsing this ML archives, as there's many posts about why projects were removed from TM2. Frankly I used TM1 projects at very beginning I was using TM1, but since I started rely seriously on SCM (GIT in fact) I do not use them anymore at all.
One thing that would make TM2 more pleasant for these, who are used to projects, is symlinks to folders being expandable, not just being clickable as it is now.
Cheers,
On Feb 2, 2012, at 7:06 AM, jomifo wrote:
So one of the things I did often in TM1 was create projects with files that are located all over the file system. Seems like projects in TM2 are based off of a single folder, but I admit I don't understand the .tm_properties stuff that well yet.
The elimination of projects is certainly one of the most disconcerting aspects of TM2 and has been discussed before on the list, without any resolution. Using Favorites with aliases is not a suitable substitute for several reasons. I don't know how susceptible Alan is to lobbying on this but I hope it doesn't hurt to keep trying. Jerry
Is there a way to use .tm_properties to do what I did in TM1? If so, can someone post an example .tm_properties?
Thanks.
View this message in context: http://old.nabble.com/TM2%3A-projects-with-scattered-files--tp33250354p33250... Sent from the textmate users mailing list archive at Nabble.com.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
You don't mention this explicitly, so have you tried just using aliases? I.e. creating a folder which represents your old project folder, and then aliasing things from there?
Using Favorites with aliases is not a suitable substitute for several
reasons.
Can you give the reasons? They might be easy to get around using new features of TM2, or by adding new features to TM2 which don't rely on the project construct.
I do agree with the project removal changes, even though I did use the feature a lot; but this is likely because I have managed to adapt my setup, and it now works better than in TM1.
David.
On Feb 3, 2012, at 5:54 AM, David Howden wrote:
On Feb 2, 2012, at 6:14 PM, Jerry wrote:
The elimination of projects is certainly one of the most disconcerting aspects of TM2 and has been discussed before on the list, without any resolution. Using Favorites with aliases is not a suitable substitute for several reasons.
Can you give the reasons? They might be easy to get around using new features of TM2, or by adding new features to TM2 which don't rely on the project construct.
I haven't been following the discussion WRT this particular change very carefully, but I'm curious: a helpful technique when doing sysadmin work is to initialize a Mercurial (or Git) repository at the root of the filesystem (or, say, in /etc), and then to use the following .hgignore file:
syntax: glob *
adding those config (or other) files you want to manage on an individual basis. The result is very much like a TM1 project containing just selected files from across the boot volume. When I first saw the introduction of Git/Hg-style configuration in TM2, I just assumed that this same technique would be possible by using the appropriate file filtering keys in .tm_properties. If so, this would seem to replicate any missing functionality lost by dropping projects files.
Am I missing something here?
-- Phil
On 03/02/2012, at 07.14, Jerry wrote:
The elimination of projects is certainly one of the most disconcerting aspects of TM2 and has been discussed before on the list, without any resolution. Using Favorites with aliases is not a suitable substitute for several reasons. I don't know how susceptible Alan is to lobbying on this but I hope it doesn't hurt to keep trying.
As long as “lobbying” is done by educating me about the flaws of the file system based approach or the (lost) advantages of the closed media library approach.
Though many things have already been said about the respective pros and cons, so it might be better to start a wiki page and collect the information instead of repeating what has already been said (or simply claiming that the loss of projects is disconcerting).
Given how much is on the to-do and the arguments I have voiced relating to this (a big one being that relying on the file system makes it more compatible with other systems such as version control, build systems, deployment (e.g. rsync), and similar), it’s probably futile though to get me to actually implement a project system in 2.0, so better chance this will appear as a third party solution via expected API for custom data sources in the file browser.
Note though that not doing a “media library” is not the same as not addressing possible shortcomings with the file system based approach.
So after playing around a bit in TM2, I think creating symlinks/aliases in a project folder should be able to replace the project functionality in TM1 that I used.
One thing that didn't work properly though was invoking subversion commands on the aliased files. It complains about the file not being in a working copy folder. I think TM2 should run the svn command on the source path, not the path of the alias.
Thanks.
jomifo wrote:
So one of the things I did often in TM1 was create projects with files that are located all over the file system. Seems like projects in TM2 are based off of a single folder, but I admit I don't understand the .tm_properties stuff that well yet.
Is there a way to use .tm_properties to do what I did in TM1? If so, can someone post an example .tm_properties?
Thanks.
On 2012-02-03 10:39, jomifo wrote:
One thing that didn't work properly though was invoking subversion commands on the aliased files. It complains about the file not being in a working copy folder. I think TM2 should run the svn command on the source path, not the path of the alias.
It might be good to have some sort of option for that, but in general it's not workable. Subversion (and I assume Mercurial and Git) allows you to put symlinks themselves under version control. Maybe some heuristic like:
if file is symlink: if symlink is under version control: act on symlink else if target is under version control: act on target
Seems like it'd need a lot of special cases though, and possibly some sort of manual override as well. It's a messy work-around for something that used to be easy.
(Forgive me if there's something special about MacOS's aliases. AFAIK, aliases are just another mechanism to implement symlink functionality left over from the pre-OSX days.)
-
Adam Strzelecki -
Allan Odgaard -
David Howden -
Jerry -
jomifo -
Phil Schumm -
Steve King