cm0002@piefed.world to Programmer Humor@programming.devEnglish · 7 days agoExit Signlemmy.mlimagemessage-square72fedilinkarrow-up1917arrow-down111 cross-posted to: programmerhumor@lemmy.ml
arrow-up1906arrow-down1imageExit Signlemmy.mlcm0002@piefed.world to Programmer Humor@programming.devEnglish · 7 days agomessage-square72fedilink cross-posted to: programmerhumor@lemmy.ml
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up13·7 days agoNo, it isn’t, x writes only when changes have been made, while w writes unconditionally.
minus-squarejosefo@leminal.spacelinkfedilinkarrow-up1arrow-down1·6 days agoWhy would you want to write again if no changes were made? It’s some obtuse behavior
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up5·6 days agoOne obvious use-case is to cause the file to get a new timestamp, which for example tools like make look at.
Also :x is the same as :wq
No, it isn’t, x writes only when changes have been made, while w writes unconditionally.
TIL. Ty!
Why would you want to write again if no changes were made? It’s some obtuse behavior
One obvious use-case is to cause the file to get a new timestamp, which for example tools like make look at.