The Most Dangerous Writing App • Hacker News Board

Re: The Most Dangerous Writing App

#191

Post by Breza » Sun, Aug 25, 2019, 4:59 AM UTC

tripzilch wrote: post #133

lostjohnny wrote: post #53

Earlier quoted context omitted.

I think everyone older than 30 does. I also have the habit of pressing it more than one time, every time I press it. I'm not even be sure that save will really save.

I do this for ctrl-C copying, because for a short while, years ago I had a keyboard where the C-key would occasionally fail. I have long since replaced this keyboard, but the habit of just hitting ctrl-C more than once is not entirely gone.

I had a similar problem about a decade ago. My muscle memory for editable text became CTRL-X CTRL-V so I could see the the text had been copied.

Re: The Most Dangerous Writing App

#192

Post by stevewodil » Mon, Aug 26, 2019, 3:13 PM UTC

astrodust wrote: post #189

stevewodil wrote: post #188

Earlier quoted context omitted.

Several times? No, just saving once is sufficient.

Why not twice to be sure?

Because most programs don't do anything if no changes were made between the current state and the last save. VS Code shows which files have changes made since the last save, for example.

Re: The Most Dangerous Writing App

#193

Post by astrodust » Mon, Aug 26, 2019, 8:54 PM UTC

stevewodil wrote: post #192

astrodust wrote: post #189

Earlier quoted context omitted.

Why not twice to be sure?

Because most programs don't do anything if no changes were made between the current state and the last save. VS Code shows which files have changes made since the last save, for example.

Exactly why it doesn't hurt to save a bunch of times to be sure.