Project settings not being applied

[jpcirrus]

When worksheet settings are applied in .sublime-project they are not being applied.

To test: add the Python virtualenv settings from README.md to a project's settings, but change the prefix (and cmd path to the virtualenv python) to have an additional > like so:

"settings": {
    "worksheet_languages": {
        "Python": {
            "cmd": "/path/to/virtualenv/bin/python -i",
            "prompt": [">>> ", "\\.\\.+ "],
            "prefix": "# >> ",
            "error": ["Traceback ", "  File \"<stdin>\","]
        },
    }
}

Then evaluate a Python view and the project specific prefix is not used. This applies to the other settings as well. It also makes no difference if Sublime is started from the shell in an active virtualenv.

This is with ST2 2.0.2, build 2221 on OS X and sublime-worksheet a153ad8972

[jcartledge]

Thanks.

I think there are some funky things happening with settings - ill take a look. Thanks for the test case.

[jakeonrails]

I can confirm the same.

I've tried using project settings, editing the USER worksheet.sublime-settings, and I even tried unzipping the local worksheet plugin, modifying the base settings file, and rezipping (that removed the plugin from sublime text, unfortunately).

All I want is to change the ruby from irb to use /usr/bin/env irb so that it will pick up my RVM installation instead of System Ruby, which doesn't have the proper gems installed.

Any luck on this settings bug?