It'd be great if there were side kind of feedback, like the cursor quickly flashing a "C" or something... anything to let you know the operation occurred; better yet, was successful.

[–] DrDeadCrash@programming.dev 4 points 9 months ago

Check for an asterisk after the file name (in the tab/title bar), it means "unsaved changes".

[–] kbotc@lemmy.world 4 points 9 months ago

I actually disagree from a systems engineer perspective: The program doesn’t actually know shit if those bits hit any permanent medium, just that the OS told them “I’ll take care of it” it could be sitting in a write back cache when you save, see the “write complete” and rip the power and that’s all gone now. Basically, I don’t like promising durability when it’s not really there.