Breaks build systems that rely on `$project_path`.

[jemc]

I have build systems that rely on running a command with the working_dir set to $project_path. This is defined in sublime text to be the path to the project file. Without the Project Manager plugin, this is the same as the project directory. However, with the Project Manager plugin, new projects go in your central projects folder (which is what I want), but $project_path in the context of build systems also points to the central projects folder (which is not what I want).

Ideally, Project Manager would somehow set $project_path to the target project directory for build systems.

[randy3k]

If this is the case, I suggest you to import your own ".sublime-project" file instead of letting Project Manager to handle it. Check the first bullet of https://github.com/randy3k/Project-Manager#add-existing-projects-to-project-manager

[jemc]

Not having to carry the project file in the project directory is my main use case for Project Manager - none of the other features are particularly useful to me, and loading is slower than "native" project loading.

[randy3k]

I couldn't find an easier solution for this issue. Any suggestions would be appreciated.

[chenxxzhe]

Could you add a new property project_root in .sublime-project file and map this to $project in sublime?

[randy3k]

We would add a new property to the project data but it seems that there is no known way to set the $project variable.

[randy3k]

Just a note for further readers, instead of $project_path, you may want to use $folder, the first folder of the current window.