Waffelson@lemmy.world to linuxmemes@lemmy.world · 1 year ago:wq!lemmy.worldimagemessage-square14fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1image:wq!lemmy.worldWaffelson@lemmy.world to linuxmemes@lemmy.world · 1 year agomessage-square14fedilink
minus-squareGoku@lemmy.worldlinkfedilinkarrow-up0·1 year agoWhy do so many people prefer :wq over :x?
minus-squarelars@lemmy.sdf.orglinkfedilinkarrow-up1·1 year ago:x was a gamechanger. And it doesn’t update the file’s modify date if you made no changes. Sometimes I just sit back and think about all that saved time and effort so much that I have actually lost time by switching from :wq.
minus-squarerwhitisissle@lemmy.worldlinkfedilinkarrow-up1·1 year agoBecause :wq to me means “Issue command write, followed by command quit.” “Issue command x” to me means nothing in the context of vim, and ctrl + x on most systems is reserved for cutting, so it just “feels” wrong.
Why do so many people prefer :wq over :x?
:x
was a gamechanger. And it doesn’t update the file’s modify date if you made no changes.Sometimes I just sit back and think about all that saved time and effort so much that I have actually lost time by switching from
:wq
.Because :wq to me means “Issue command write, followed by command quit.” “Issue command x” to me means nothing in the context of vim, and ctrl + x on most systems is reserved for cutting, so it just “feels” wrong.