Waffelson@lemmy.world to linuxmemes@lemmy.world · 9 months ago:wq!lemmy.worldimagemessage-square116fedilinkarrow-up1221arrow-down172
arrow-up1149arrow-down1image:wq!lemmy.worldWaffelson@lemmy.world to linuxmemes@lemmy.world · 9 months agomessage-square116fedilink
minus-squareMiku Luna \ she/it@lemmy.blahaj.zonelinkfedilinkarrow-up22·9 months agoyou don’t need the ! when you have the w, because your changes already get saved.
minus-squareraptir@lemdro.idlinkfedilinkEnglisharrow-up18·9 months agoIf anything it is dangerous as it will still exit even if changes cannot be saved.
minus-squareDocMcStuffin@lemmy.worldlinkfedilinkarrow-up6·9 months agoTry editing a file in /etc as a regular user. It happens sometimes and you really want that warning that the write failed. Anyway, :x is superior. It only writes if there are changes. So, your mtime doesn’t change unnecessarily.
minus-squareMiku Luna \ she/it@lemmy.blahaj.zonelinkfedilinkarrow-up4·9 months agowait people care about the mtime?
minus-squarecarcus@lemmy.mllinkfedilinkEnglisharrow-up4·9 months agoI’ve had to do forensics on a rogue change. In finding when and who actually changed the file, mtime can help narrow it down when compared with wtmp.
you don’t need the
!
when you have thew
, because your changes already get saved.If anything it is dangerous as it will still exit even if changes cannot be saved.
Try editing a file in
/etc
as a regular user. It happens sometimes and you really want that warning that the write failed.Anyway,
:x
is superior. It only writes if there are changes. So, your mtime doesn’t change unnecessarily.wait people care about the mtime?
I’ve had to do forensics on a rogue change. In finding when and who actually changed the file, mtime can help narrow it down when compared with wtmp.