@Waffelson@lemmy.world to linuxmemes@lemmy.world • 1 year ago:wq!lemmy.worldimagemessage-square110fedilinkarrow-up1227
arrow-up1227image:wq!lemmy.world@Waffelson@lemmy.world to linuxmemes@lemmy.world • 1 year agomessage-square110fedilink
minus-square@EuroNutellaMan@lemmy.worldlinkfedilink12•1 year agoCause I don’t like to think about my x
minus-square@rwhitisissle@lemmy.worldlinkfedilink8•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.
minus-square@lars@lemmy.sdf.orglinkfedilink5•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-square@AVincentInSpace@pawb.sociallinkfedilinkEnglish1•1 year agosame reason I prefer :wq to ZZ. muscle memory.
Why do so many people prefer :wq over :x?
Cause I don’t like to think about my x
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.
: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
.why not?
same reason I prefer :wq to ZZ. muscle memory.
There is a other option?