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
{{ message }}
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
Paxton, please check this in your system. Open a non-proxy project which .ml-sublime-options file is configured to connect to say, db1. With the first project loaded, then open another non-proxy project which .ml-sublime-options file is configured to connect to say, db2. Do they both work ok as you go back and forth between them?
In my system, the first loaded project's options file (db1) trumps over the second loaded project's options file (db2). I had to actually re-start Sublime and open the original second project (db2) first to have its options file actually be "seen" by Sublime.
The text was updated successfully, but these errors were encountered:
Using Sublime 3 (build 3065) on Mac OS 10.7.5.
Paxton, please check this in your system. Open a non-proxy project which
.ml-sublime-options
file is configured to connect to say, db1. With the first project loaded, then open another non-proxy project which.ml-sublime-options
file is configured to connect to say, db2. Do they both work ok as you go back and forth between them?In my system, the first loaded project's options file (db1) trumps over the second loaded project's options file (db2). I had to actually re-start Sublime and open the original second project (db2) first to have its options file actually be "seen" by Sublime.
The text was updated successfully, but these errors were encountered: