rustydrd@sh.itjust.works to Programmer Humor@lemmy.mlEnglish · 1 year agoJust to be safesh.itjust.worksimagemessage-square41fedilinkarrow-up1413arrow-down118
arrow-up1395arrow-down1imageJust to be safesh.itjust.worksrustydrd@sh.itjust.works to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square41fedilink
minus-squareProgrammer Belch@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up24·1 year agoMy muscle memory is too strong from years of vscode before vim so I have :w mapped to C-s
minus-squarerustydrd@sh.itjust.worksOPlinkfedilinkEnglisharrow-up29·1 year agoThis is Vim’s evil mode
minus-squareAccountMaker@slrpnk.netlinkfedilinkarrow-up5·1 year agoI have the opposite situation, I had to willingly stop myself from typing :w while using Word. And I installed the vim extension in vscode, which leads to me typing :w when using someone else’s setup.
minus-squareProgrammer Belch@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·1 year agoI still get lots of jkhl after some lines when I’m trying to move between lines
minus-squareUNWILLING_PARTICIPANT@sh.itjust.workslinkfedilinkarrow-up5·1 year agoHissss we’re enemies
My muscle memory is too strong from years of vscode before vim so I have
:wmapped toC-sThis is Vim’s evil mode
I have the opposite situation, I had to willingly stop myself from typing :w while using Word. And I installed the vim extension in vscode, which leads to me typing :w when using someone else’s setup.
I still get lots of jkhl after some lines when I’m trying to move between lines
Hissss we’re enemies