Allan Odgaard 6c48d1d9d7 Always set variable for commands with requirements ...

Previously we would only set the variable if the command couldn’t be found via PATH. By always setting the variable, we remove redundancy from commands, as they can now rely on the variable instead of needing fallback code (to load via PATH).

The downside is that there are cases where a command may wish to know if the user explicitly set the variable, for example the Run command for Python will ignore the script’s shebang if the user explicitly set TM_PYTHON. As this command doesn’t use the requirement system, it’s not an actual problem. Should it want to specify the requirement, it can do so by using a variable like TM_PYTHON_AUTO and then in the locations array, set TM_PYTHON, this would allow the command to test if TM_PYTHON is set and if not, still have ‘python’ available via the TM_PYTHON_AUTO variable — although, should python not be found, the error dialog will tell the user to set TM_PYTHON_AUTO.

Issue #767

2013-02-18 21:55:59 +01:00

..

resources

Make encoding “hex view” wider

2013-02-18 15:38:26 +01:00

src

Always set variable for commands with requirements

2013-02-18 21:55:59 +01:00

target

Make DocumentOpenHelper API block-based

2013-01-08 22:48:06 +01:00