Closed tesseslol closed 7 years ago
That's weird, the variable is definitely there initially. There's probably some bad logic with how custom.less
is getting generated from the package settings. I'll try to get it sorted out tonight.
Ew, looks like something in the 1.14.4 update broke it. I guess that's what I get for hacking in configurable styles ¯\(ツ)/¯
Pushed a quick patch that disables the "Transition Duration" setting so the plugin at least loads. After updating to 1.3.2
there shouldn't be any warnings, only change is that your minimap will slide out in 100ms, regardless of what's in your settings.
Just pushed 1.3.3
, which should fix the issue. I'm still not really sure what was causing the less variable not to be initialized after an update. I'm just going to go ahead and assume it was a race condition, which I've fixed by adding a default.less
file that initializes the variable. That way, the variable will always be set to something, which should avoid that specific crash. Until atom adds some kind of real connection to the settings page from less
, this will continue to be super hacky. Closing for now, let me know if the issue persists after updating.
Thanks for the report @tesseslol!
[Enter steps to reproduce:]
Atom: 1.14.4 ia32 Electron: 1.3.13 OS: Unknown Windows version Thrown From: minimap-autohider package 1.3.1
Stack Trace
Failed to load the minimap-autohider package
Commands
Non-Core Packages