You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the SublimeREPL repo, "On POSIX system SublimeText launched from GUI does not inherit a proper environment. Often leading to problems with finding interpreters or not using the ones affected by changes in ~/.profile / *rc files".
Though this is a Sublime bug, it has the effect that Merlin often doesn't work for people who open their ml files using the Sublime GUI.... the ocamlmerlin binary often can't be found. The SublimeREPL folks have added a workaround to their plugin. It might be nice to do similar here.
Or, it might be worth documenting that users running into trouble when opening files from the GUI should manually set "ocamlmerlin_path" in their Merlin package user settings.
The text was updated successfully, but these errors were encountered:
Indeed, manually setting ocamlmerlin_path fixes this wrong behavior. I currently think that documenting the ocamlmerlin_path variable is easier than starting to update environment variables provided by ST, but will have a look at the solution from SublimeREPL.
Meanwhile, if you want to provide a solution or update the README file, your contribution is welcome. 😄
As mentioned in the SublimeREPL repo, "On POSIX system SublimeText launched from GUI does not inherit a proper environment. Often leading to problems with finding interpreters or not using the ones affected by changes in ~/.profile / *rc files".
Though this is a Sublime bug, it has the effect that Merlin often doesn't work for people who open their ml files using the Sublime GUI.... the ocamlmerlin binary often can't be found. The SublimeREPL folks have added a workaround to their plugin. It might be nice to do similar here.
Or, it might be worth documenting that users running into trouble when opening files from the GUI should manually set "ocamlmerlin_path" in their Merlin package user settings.
The text was updated successfully, but these errors were encountered: