Five lines I put in a blank .vimrc

Post by JoshTriplett » Sun, Dec 13, 2020, 10:22 PM UTC

toxik wrote: post #4

I'd prefer one line it and use the "long" names and add nocompatible set nocompatible hlsearch incsearch ignorecase number then sane tabs set et sts=4 sw=4

    set expandtab
    set shiftwidth=4
    set softtabstop=4
    function Spaces(...)
        if a:0 == 1
            let l:width = a:1
        else
            let l:width = 4
        endif
        setlocal expandtab
        let &l:shiftwidth = l:width
        let &l:softtabstop = l:width
    endfunction
    command! T setlocal noexpandtab shiftwidth=8 softtabstop=0
    command! -nargs=? S call Spaces()
    autocmd BufNewFile,BufRead ~/src/linux/* T
    autocmd BufNewFile,BufRead ~/src/git/* T
    autocmd FileType html S 2
    autocmd FileType tex S 2

Post by strogonoff » Sun, Dec 13, 2020, 10:25 PM UTC

SoSoRoCoCo wrote: post #30

strogonoff wrote: post #5

Why not one line? set hls ic is nu noswf On a serious note, personally disabling line numbers is the first thing I do in a new editor. Reduces visual noise—status line usually shows current line number anyway, jumping to a line might take a second and I found I don’t need to know my line numbers more frequently than once per month or so. What I do like to enable in an editor is visible whitespace characters (helps no…

Line numbers are great, until you try to cut and paste. But then again, VI/M wasn't designed for GUIs.

Post by OJFord » Sun, Dec 13, 2020, 10:29 PM UTC

lucb1e wrote: post #21

The swap file saved my work a number of times. If you never use recover and use Vim regularly, then go ahead and disable it; if you haven't used it because you don't know how to use it or you only rarely use Vim, then I'd encourage you to either try it first or leave it enabled (as it is by default) until it becomes a nuisance. And like u/strogonoff, I also disable line numbers, but that's just personal preference of…

Post by toxik » Sun, Dec 13, 2020, 10:30 PM UTC

kolme wrote: post #22

pletnes wrote: post #10

Earlier quoted context omitted.

Why nocompatible?

Not necessary, AFAIK, unless you invoke vim using the alias "vi". If you call "vim" it'll start in nocompatibe mode by default. The nocompatible mode means adding some features to vim rendering it "incompatible" with the original vi. For example in the original vi you can only undo the last action, with compatible mode on vim will mimic this behavior.

Post by ogre_codes » Sun, Dec 13, 2020, 10:31 PM UTC