Thanks for the great module. Running into a problem though at the moment. It's happening on more than one machine (Win10 and Win7) and with differing Atom versions on each (fresh beta install and stable).
It occurs when re-opening a project with a js file already loaded in a tab (i.e. Atom was closed with that tab open). I get the "Something went wrong internally" message which appears to be due to the settings object not being pulled from cache correctly (or something like that, at a glance).
It's quite the annoying bug since it messes up the scrollbars / editor view and requires re-opening the files every time. (Scrollbars is an Atom issue, unrelated but happened to coincide)
Is there anything I can get you / do to help debug this?
Thanks for the great module. Running into a problem though at the moment. It's happening on more than one machine (Win10 and Win7) and with differing Atom versions on each (fresh beta install and stable).
It occurs when re-opening a project with a js file already loaded in a tab (i.e. Atom was closed with that tab open). I get the "Something went wrong internally" message which appears to be due to the settings object not being pulled from cache correctly (or something like that, at a glance).
It's quite the annoying bug
since it messes up the scrollbars / editor view andrequires re-opening the files every time. (Scrollbars is an Atom issue, unrelated but happened to coincide)Is there anything I can get you / do to help debug this?