by Iuz on 2/9/17, 12:58 PM with 204 comments
by a-b on 2/9/17, 4:24 PM
When vi was originally designed the most popular keyboard was ADM-3A and later IBM XT https://en.wikipedia.org/wiki/IBM_PC_keyboard#/media/File:IB... The layout of this keyboard has Control on the place where modern keyboards have a CapsLock key. Naturally that's why vi and vim was meant to use CTRL-[ to exit to the normal mode.
25 years later Apple introduced ToughBar and made ESC key virtual. As result remapped CapsLock-[ make sense again ;)
edit: Add ADM-3A keyboard
by robteix on 2/9/17, 4:26 PM
He said something that I always found interesting. He was talking about how in a decade or so we would probably be using software and tools that would be unrecognizable to us at that moment, but after a pause he added: "but we'll still be writing code with vi." :)
by a-b on 2/9/17, 4:27 PM
• http://vim.spf13.com this distribution is remarkable! Extremely well documented vimrc file is a great source of knowlege by itself https://github.com/spf13/spf13-vim/blob/3.0/.vimrc
• https://github.com/carlhuda/janus
Also, it worth to mention
and
by jmcdiesel on 2/9/17, 6:01 PM
Consider the case of people like me who work on remote servers, who spin up new vagrant boxes and work on them remote... with the package manager as he described it, i'd have to download all the plugins and manually place them, etc... as i currently stand, i install vundle really quickly , then it just reads my .vundlerc.bundles and installs all the plugins i want, presto. Half solutions are worse than no solutions... because now people will compare the two, and default (likely) to the default solution and make package management harder on themselves than it needs to be...
by shmerl on 2/9/17, 10:03 PM
I switched to neovim a while ago, because it supported 24-bit color themes in the terminal. Since then it seems even regular vim picked it up too. It's good to see that some pressure moved the project forward in different areas which were stuck forever before.
Though neovim already uses XDG base directory specification, but vim still doesn't.
by a-b on 2/9/17, 4:42 PM
by jmcdiesel on 2/9/17, 5:58 PM
I feel bad, in a way, because i have a strong loyalty to vim, but Bram's stubbornness at playing well with others is basically holding onto sand, and we know how that analogy goes...
by a-b on 2/9/17, 4:43 PM
by Keyframe on 2/9/17, 6:40 PM
by ivanche on 2/9/17, 4:09 PM
by smhenderson on 2/9/17, 4:42 PM
^ no disrespect to emacs though, it is also a great and venerable program!
by 6ftdan on 2/10/17, 1:06 PM
I've also built this into a remote programming Docker image: https://hub.docker.com/r/danielpclark/ruby-pair/
by a-b on 2/10/17, 4:03 AM
It works great considering that
:s//new_pattern/g
will search for last /old_pattern
by CaliforniaKarl on 2/9/17, 4:48 PM
I'd say the most advanced stuff I do is gqap, and performing substitutions via regex, either with a range or in visual mode.
I'd appreciate suggestions as to the best path to take, to move to a more advanced level of Vim 8. (Note I mention Vim 8 explicitly. Also, if extending my existing vimrc becomes a thing to do, I'd want to do it myself, learning what each not does!)
by _nato_ on 2/9/17, 5:52 PM
by YeGoblynQueenne on 2/9/17, 6:22 PM
Also:
https://github.com/idanarye/vim-smile
Vim now has a ":smile" command :D
by adtac on 2/9/17, 4:23 PM