New answers tagged

5

When you use the += operator, you actually ask vim to append some new values to the statusline variable. When you first open Vim statusline is set to an emtpy value so adding %.35f to it give you the expected behavior. However when you source your config again, nothing empties the variable so you keep adding duplicate values to it. Thus you probably want to ...


0

Some [lightly edited] info from the comments: Actually this might be the reason for empty Quickfix window. On your screen cast when you run :lopen, Neomake runs for that buffer due to the autocmd for BufEnter. It should be additionally limited to JavaScript files only: augroup neomake au! autocmd BufWritePost *.js Neomake augroup END


1

I inject my own way of opening files in COC with let g:coc_user_config = {} let g:coc_user_config['coc.preferences.jumpCommand'] = ':SplitIfNotOpen4COC' Then the command is defined in my lh-vim-lib plugin to search if the buffer is already opened or not. Having more control is possible. To use the prompt already provided by COC, you may have to search ...


0

I finally resolved this by installed python-language-server globally like this: sudo -H pip install python-language-server I don't know how popular a solution this will be, but it works for me, so I'm happy.


0

After a quick google, I found this, which suggests this is not a coc.nvim issue, but a typescript configuration issue. my understanding is you'd need to provide the typeCheck: true config option to ts-loader, at the cost of tslint running slower That said, the issue hasn't had much activity in a year.


5

I don't use fzf and use Vim instead of neovim. So I couldn't reproduce your scenario. Also I was not able to reproduce what @dedowsdi described in his comment.(See end of answer.) But some general stuff around autocmd and feedkeys: Assume we open Vim with three new files in split windows: vim -O a.txt b.txt c.txt Vim will open with three windows like ...


Top 50 recent answers are included