I would like some snippets to only be in scope for a specific project. For instance, some tab-expansions I'd like to choose for a snippet only make sense for C++ files part of project Foo, but not all C++ files. So I'd like to be able to specify the scope to be something like:
project:Foo.source.cpp
Instead of just
source.cpp
Thus narrowing the snippet to only the source.cpp scope for files in project Foo.
Perhaps allowing a user to add a project scope identifier and use this in scope specifications would be the way to implement this. Heck, that would allow anything that depends on a specific scope to be project-specific if the user wants. Templates, commands, macros.. Sounds like fun to me ;-)
On 08/09/2005, at 21.36, Corey O'Connor wrote:
Perhaps allowing a user to add a project scope identifier and use this in scope specifications would be the way to implement this. Heck, that would allow anything that depends on a specific scope to be project-specific
I've had a request for project specific bundles, which I think would be a better solution. I.e. letting bundles be loaded more dynamically, and having $TM_PROJECT_DIRECTORY/Bundles be one of the search locations.
That way, one doesn't need to update all scopes when moving something to a project (e.g. copy it from an old project, renaming the project etc.).
It's not a high-priority thing, but I do need to revamp current bundle handling (eventually), and when I do, it probably wouldn't be that much extra effort to allow bundles to be loaded from (and rely upon) a given project -- my main concern is only how to do the interface for this.
On 9/8/05, Allan Odgaard allan@macromates.com wrote:
I've had a request for project specific bundles, which I think would be a better solution. I.e. letting bundles be loaded more dynamically, and having $TM_PROJECT_DIRECTORY/Bundles be one of the search locations.
w00t. Sounds great. I'd be perfectly happy with that. :-)
-
Allan Odgaard -
Corey O'Connor