VulcanSphere@kbin.social to Technology@lemmy.world · edit-21 年前RIP Bram Moolenaar, the author of vim text editorgroups.google.comexternal-linkmessage-square62fedilinkarrow-up1996arrow-down113file-textcross-posted to: vim@lemmy.sdf.orglinux@lemmy.mlleftistunix@lemmygrad.mlcoweram@bin.pztrn.onlinetechnology@beehaw.orgtech@kbin.sociallinux@kbin.socialvim@lemmy.sdf.orglinux@lemmy.ml
arrow-up1983arrow-down1external-linkRIP Bram Moolenaar, the author of vim text editorgroups.google.comVulcanSphere@kbin.social to Technology@lemmy.world · edit-21 年前message-square62fedilinkfile-textcross-posted to: vim@lemmy.sdf.orglinux@lemmy.mlleftistunix@lemmygrad.mlcoweram@bin.pztrn.onlinetechnology@beehaw.orgtech@kbin.sociallinux@kbin.socialvim@lemmy.sdf.orglinux@lemmy.ml
minus-squaretwistypencil@lemmy.worldlinkfedilinkEnglisharrow-up19arrow-down1·1 年前Technically, that is not vim specific, conning from sed and ed, but definitely worked in vim as well as all vi clones
minus-squarechinpokomon@lemmy.worldlinkfedilinkEnglisharrow-up5·1 年前This is why it works so well. It’s also one of the reasons I prefer vi over other text editors. It isn’t always the most logical which commands and keys do what, but I like the consistency.
Technically, that is not vim specific, conning from sed and ed, but definitely worked in vim as well as all vi clones
This is why it works so well. It’s also one of the reasons I prefer vi over other text editors. It isn’t always the most logical which commands and keys do what, but I like the consistency.