Hacker News new | ask | show | jobs
by mstade 3561 days ago
> Those $70 are definitely worth every penny.

I've said it before, and I'll say it again – the fact that ST saves buffers no matter what has saved my butt so many times I can't even count. The effort it would've taken to restore the lost data had those buffers not been stored would've costed way more than $70 every time. Even if ST was worse in every possible way than other editors (and it's not,) I'd still pay money for this (and I did.)

I don't know if my license will stop working when ST3 comes out of beta (I think I bought it for ST2, but it was so long ago at this point I don't even know) but if it does I'll happily shell out another $70. ST is one of the few tools I use that never, ever caused me any grief. Not once. It just works, works really well, and does all I need it to do.
1 comments
TheRealDunkirk 3561 days ago
Agreed. The ability to paste some data I may or may not need after a couple more hours of debugging, and have that buffer save through a reboot -- without needing to save it to a file -- is something I've come to rely on. I only realized this when I tried Visual Studio Code, and noticed that it wasn't doing the same thing.
link
glogla 3561 days ago
This is the reason I stopped using Atom and returned to ST. It's just so practical.
link
matt_kantor 3561 days ago
For anyone else who is missing this feature from Atom, try the save-session package.
link
jdi 3561 days ago
I see on the package page that all its functionality has been merged into Atom itself.
link
radafor 3560 days ago
I noticed that too, but for some reason I can't seem to figure out how exactly it works. It's not just like in ST, as my buffers get lost. After a while I just gave up because I don't actually need to switch from ST...
link
matt_kantor 3560 days ago
There's a confusing bug related to this feature. Currently, Atom only automatically re-opens unsaved buffers in "project" windows (those associated with a particular directory). See https://github.com/atom/atom/issues/10474 for details. It's a real bummer and I hope it gets fixed soon.
link
matt_kantor 3561 days ago
Ah, right! Now that you mention it I remember following that ticket. I must've neglected to remove the package after that happened.
link