Jongwook Choi

@yatli Also check out this workaround https://github.com/neoclide/coc.nvim/issues/668#issuecomment-481975596 suggested by @mars90226.

@justinmk Yes, it is. (tested on NVIM v0.4.0-1197-gff95e62ff, by disabling the patch from neoclide/coc.nvim#668)

It might be debatable whether gitsigns should trigger FugitiveChanged directly, or we may want to define and introduce a custom user-autocmd event (please let me know of your preference!). This...

+1 I also think gitsigns.nvim should trigger `FugitiveChanged` (**by default** or via configuration) when doing operations like stage_hunk, reset_hunk, etc.

FYI the current workaround I ended up using is: ```lua lsp_setup_opts['sumneko_lua'] = vim.tbl_deep_extend('force', require("lua-dev").setup {}, { settings = { Lua = { completion = { callSnippet = "Disable" }, workspace...

@erwin I don't think your settings is correct. `require("lua-dev").setup{}` and `{...}` are supposed to be merged to `opts`, but they aren't. `opts` should be used later like `server:setup(opts)`, but it...

~Also, the position and the height of a scrollbar is determined by the actual line number (not fully aware of folding). This makes the movement of the scrollbar not uniform...

Thanks. We would need an autocmd event for fold updates for this. As a side note, how about providing `` mappings to make custom keymaps much easier?

Thank you @dstein64! That was exactly I was figuring. For now, I will need to use this keymap-based workaround to trigger the refresh command for folding-related actions.

Upstream neovim issue for "fold" update events: https://github.com/neovim/neovim/issues/8538