History and Effective Use of Vim

Post by kerkeslager » Sat, Jul 20, 2019, 2:59 PM UTC

Legogris wrote: post #182

kerkeslager wrote: post #176

Earlier quoted context omitted.

> But why wouldn't you want the Vim on your main driver laptop, which you use every day to not have a nice custom setup, and some good third party plugins (e.g. file search, linting, etc)? There are two assumptions I think you're making here: Assumption 1: You can do better than the defaults enough to justify the costs of optimizing. I use a pretty much default vim configuration as my primary development environment,…

I have a specific counterexample: softtabs and tabstop. vim uses tabs by default I have to be conscious of when to use tabs vs spaces. With some configuration to detect it by file type, this (for me significant) overhead is removed.

    " Set tabs to width 2.
    filetype plugin indent on
    set shiftwidth=2
    set softtabstop=2
    set tabstop=2
    set expandtab

    " language-specific settings: tab width is 4 for python
    autocmd FileType python setlocal shiftwidth=4 softtabstop=4 tabstop=4

Post by JadeNB » Sat, Jul 20, 2019, 3:32 PM UTC

root_axis wrote: post #34

2bitencryption wrote: post #2

After years of a love/hate relationship with Vim (I love what it does, but have configuring it), I had an epiphany: by sticking with the defaults, whether they are my preferred choices or not, I can instantly understand how to use Vim in any environment. Once you get used to biting the bullet and hitting escape instead of jj, or ctrl+c, it just works, everywhere. If you abandon the urge to pimp out your Vim with a bi…

This makes sense if you don't use vim as an IDE, but if you do, configurations and plugins are essential. Of course, you wouldn't expect to have a fully configured jetbrains IDE when you SSH into a remote server, but that doesn't mean you can't use one on your local development machine.

Post by deergomoo » Sat, Jul 20, 2019, 4:40 PM UTC

alskdj21 wrote: post #101

deergomoo wrote: post #62

Earlier quoted context omitted.

After a several month effort to learn vim bindings and use them full-time, I eventually ended up weaning myself back off because the plugins for the editors I actually use all seemed to come with considerable downsides. vscode-vim caused odd performance issues, and I encountered significant bugs with the undo stack (namely hitting 'u' would sometimes take out the last 10-15 changes instead of just one). IDEAvim would…

You should take a look at language server clients for vim e.g. coc-nvim. I don't personally used one so I can't say what works or not. [0] https://github.com/neoclide/coc.nvim

Post by kps » Sat, Jul 20, 2019, 5:03 PM UTC

begriffs wrote: post #93

kazinator wrote: post #37

> Some of the clones: > > nvi - 1980 for 4BSD > [ ... ] > elvis - 1990 for Minix and 386BSD This is incorrect; nvi is in fact a mid 1990's fork of Elvis, worked over for better POSIX compliance by Keith Bostic. > vim - 1991 for Amiga Though that was the first public release, Moolenaar had worked on it since 1988. It was based on Tim Thompson's Stevie, which had been released, in 1987 (noted in the table).

Thanks for the correction, can you give me a more precise date for nvi? I can update the article.

Post by trcollinson » Sat, Jul 20, 2019, 6:03 PM UTC

airnomad wrote: post #155

trcollinson wrote: post #132

Earlier quoted context omitted.

It's unfortunate that in this day and age we still have people who directly access and touch a production server at all, ever. There is zero need.

You're quite green, aren't you?