News for hackers. Stuff that matters.
Re:Ten Years of Vim by dingaling on Monday May 21, 2018 @04:19AM (#17116904)
Most of those are plain vi ( and ed ) commands.

All of my machines have the vim-tiny package to stay as close to stock vi as possible. I open and close the editor dozens of times a day to make simple changes and I don't tolerate any lag.

I can see that vim would be great for long-form programming but plain old vi was just fine for most admin tasks.

Re:Ten Years of Vim by Zardoz84 on Monday May 21, 2018 @05:20AM (#17117139)
Use Plug to load the plugins that you only need for a specific file. For example, this only load this plugins if I'm working wiht LESS/SCSS/CSS or Vue files :

Plug 'groenewege/vim-less', { 'for': ['less']} Plug 'cakebaker/scss-syntax.vim', { 'for': ['scss'] } Plug 'othree/csscomplete.vim', { 'for': ['less', 'scss', 'css', 'vue'] }

Re:Ten Years of Vim by LyndsySimon on Monday May 21, 2018 @04:32PM (#17121585)
Thank you! I wasn't aware this was possible; it improves things quite a bit for me.
Re:Ten Years of Vim by bArray on Monday May 21, 2018 @04:35AM (#17116968)
Okay, so I've come across `vim.tiny` a few times now, what's the difference?

Plain `vi` I can't seem to work out, the shortcuts I usually use all seem to be different?

Re:Ten Years of Vim by majewsky on Monday May 21, 2018 @09:37AM (#17118254)
vim-tiny differs from regular vim in how much stuff is compiled into it. Regular vim is actually quite hefty since it includes e.g. scripting bindings to Python, Perl, Lua, etc.; or support for X11 (which is useful even in a terminal for working with the X clipboard), and so on. If you have both vim and vim-tiny installed, you can use the command ":version" to compare which features have been compiled in.