Open karlhorky opened 7 years ago
@Creky and I were also having this issue.
+1
I'm also having this issue. Noticed it over the past couple of weeks.
This has been persistent for a good long while.
It's a sad statement about the ecosystem, when my primary text editor breaks itself every few days. Seriously guys...
@adamlwgriffiths just uninstall the package, as the README says, the functionality is already built-in in atom, i can confirm that.. uninstall it solved the problem for me and everything is working as before.
Yeah, maybe this package should be unpublished / deleted. Or at least for versions later than the Atom where it's available in core (if that's even possible?)
i guess it is possible by specifying some kind of metadata to engines.atom
but it would require a maintainer interaction which it is likely not gonna happen because the maintainer seems inactive on github for a while.
I think I did eventually, in my quest to purge things that were perf issues.
I did manually uninstall it when I figured out it was a package. Usability is really important, and part of that is ensuring a seamless, error-free, experience. But issues like this leave a sour taste in my mouth. Manually updating and managing applications that should be self-managing is the reason I ditched Linux long ago.
As per @Ben3eeE, copied from @masajene's original issue atom/atom#15205:
Atom: 1.19.0 x64 Electron: 1.6.9 OS: Mac OS X 10.12.6 Thrown From: Atom Core
Stack Trace
Uncaught TypeError: this.promptToSaveItem(...).then is not a function
Commands
Non-Core Packages