On 27.11.2013, at 06:11 , Owen Densmore wrote:
My home folder has many folders, many of which I'd
like to have be in
multi-folder projects. So ~/bin and ~/notes are a pair, while a second
pair are ~/bank (receipts) and ~/config (a collection of configuration
files used elsewhere)
If I understand correctly, I'd have to have a .tm_properties file for each
pair, not possible given the file hierarchy style of projects
You'd want to
have a .tm_properties file in you user directory which sets the defaults. Then in many
cases, you don't need to create a per-»project« .tm_properties file.
The .tm_properties files in nested directories apply in addition to defaults. For
instance, you probably want to use different include/exclude rules in the directory where
you're writing code for a numerical simulation than in the directory where you write
the article in LaTeX with the associated findings.
Allen made a conscious design decision to abandon project files and base the idea of
projects just on filesystem hierarchy. In some ways, that makes TextMate 2 more powerful
than TextMate 1.x, but other things (especially working with scattered files) has become
more complicated because a folder is a »single project«.
Personally, I haven't found a good way to recreate my TextMate 1.x workflow in
TextMate 2 (symlinks don't mesh well with my LaTeX code and my git repositories). You
probably have to adapt the way you organize your work.
I have created a sensible master .tm_properties file and since I essentially only work
with TeX-related files, shell scripts and markdown files, I don't really need to
change them. Instead of symlinking, I just copy files and keep them in sync by hand if