Slashdot Mirror
Goodbye, Ctrl-S
An anonymous reader writes "'Save your work!' — This was a rallying cry for an entire generation of workers and students. The frequency and unpredictability of software crashes, power outages, and hardware failures made it imperative to constantly hit that save button. But in 2014? Not so much. My documents are automatically saved (with versioning) every time I make a change. My IDE commits code changes automatically. Many webforms will save drafts of whatever data I'm entering. Heck, even the games I play have an autosave feature. It's an interesting change — the young generation will grow up with an implicit trust that whatever they type into a computer will stay there. Maybe this is my generation's version of: 'In my day, we had to get up and walk across the room to change the channel on the TV!' In any case, it has some subtle but interesting effects on how people write, play, and create. No longer do we have to have constant interruptions to worry about whether our changes are saved — but at the same time, we don't have that pause to take a moment and reflect on what we've written. I'm sure we've all had moments where our hands hover over a save/submit button before changing our minds and hammering the backspace key. Maybe now we'll have to think before we write."
I've been using computers for over 30 years and have never once used this keystroke.
When it stopped meaning "Suspend output to terminal" along with it's partner CTRL-Q.
In-Band serial flow control ftw!
G.
Truly it is the year of the Linux Desktop. Long live :w
TFA doesn't mention this and, if the summary writer meant "commit" as in version control commit, this would be a killer bug in the whole process.
Version control is not meant to be used as a backup, every commit should be deliberate, reviewed and well explained in the comments. Vide the post mortem of the heartbleed bug (or many other similar ones).
That's honestly the first thing I thought of. "Saving a document" to me is "Esc-:w".
...but it's being eaten...by some...Linux or something...
I'm busy F4'ing.
Trolling is a art,
What if I don't want to save my changes?
"You can use the 'undo' command they say..."
Yes but the undo command isn't persistent between applications, much less a power failure.
You haven't solved anything, you've merely shifted the problem.
Sometimes, I don't want to save. I will open a document with the explicit purpose of making changes that I don't want saved. Even Gmail's autosave has burned me pretty badly. I spent an hour typing out a very long email. Toward the end of it, something happened, and the whole body of text was gone. I'm still not really sure if it was a keyboard shortcut I inadvertently triggered, browser bug, or what. But I just thought "no biggie... I'll just go back to the auto-saved version". So I open up the autosaved version, and the latest auto-save happened AFTER the email body was deleted. So much for autosave @#$!#$@!!!!
Esc-ZZ
This sounded so familiar to me, but I can't believe it has been over eight years ago. I must be remembering a similar story posted much more recently.
Excuses that no longer work:
My floppy disc isn't working
My computer blue screened before I saved
My e-mail was down
I don't know why your computer can't read that format
Every excuse I ever used to get a day's reprieve could not work now.
[Fuck Beta]
o0t!
Oh god, please don't tell me this is going to be the year of the Emacs Desktop?
If so I may just consider getting a job as a gardener....
Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
Apple users don't Control, they Command you insensitive clod!
... when GNU Emacs had auto-saving and backup versioning at any keystroke granularity you liked thirty years ago. Next we celebrate the boon of split screen editing.
Perhaps you've heard of a thing called a power outage.
That's where you reboot and the file is full of garbage because it crashed half-way through writing the new file to disk and the metadata was updated but not the contents, right?
Why would anyone want to autocommit possibly broken code?
...passes to Moses...SCORE!
Slow Down Cowboy! It's been 1 hour, 47 minutes since you last successfully posted a comment
Undo levels to zero, no saving. Live in the moment, on the edge. No turning back, it's all in.
Buddha does incremental backups though..
I totally had first post on this one, but I found out I actually have to click both a preview button and submit button for it to save to this forum.
Maybe they work for Adobe?
Jesus saves!
And takes half damage from the fireball.
Look at iOS - how many apps have a "save" button at all? It's expressly discouraged from the Human Interface Guidelines
With no Save, how do you Revert? Or do Apple's Human Interface Guidelines for iOS expect applications to offer unlimited undo/redo that persists across reboots of the device?
I've been pronouncing it wrong all these years.