cm0002@piefed.world to Programmer Humor@programming.devEnglish · 1 month agoExit Signimagemessage-square73linkfedilinkarrow-up1919arrow-down112 cross-posted to: programmerhumor@lemmy.ml
arrow-up1907arrow-down1imageExit Signcm0002@piefed.world to Programmer Humor@programming.devEnglish · 1 month agomessage-square73linkfedilink cross-posted to: programmerhumor@lemmy.ml
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up12·1 month agoNo, it isn’t, x writes only when changes have been made, while w writes unconditionally.
minus-squarejosefo@leminal.spacelinkfedilinkarrow-up1arrow-down1·1 month agoWhy would you want to write again if no changes were made? It’s some obtuse behavior
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up5·1 month 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.