cm0002@piefed.world to Programmer Humor@programming.devEnglish · 2 months agoExit Signlemmy.mlexternal-linkmessage-square73fedilinkarrow-up1915arrow-down112 cross-posted to: programmerhumor@lemmy.ml
arrow-up1903arrow-down1external-linkExit Signlemmy.mlcm0002@piefed.world to Programmer Humor@programming.devEnglish · 2 months agomessage-square73fedilink cross-posted to: programmerhumor@lemmy.ml
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up13·2 months agoNo, it isn’t, x writes only when changes have been made, while w writes unconditionally.
minus-squarejosefo@leminal.spacelinkfedilinkarrow-up1arrow-down1·2 months agoWhy would you want to write again if no changes were made? It’s some obtuse behavior
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up5·2 months agoOne obvious use-case is to cause the file to get a new timestamp, which for example tools like make look at.
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.