jdbann / chez Goto Github PK

fzf.vim offers all sorts of extra
functionality and mappings. Take a look, pick useful ones out and document them
somewhere. Maybe in the README of this project or at least on some paper or
post-it notes on your desk.

Some vim plugins depend on binaries installed by Yarn, Go or Ruby. When
installing a new version of one of these tools with asdf, the whole vim setup
complains because the shims that asdf indicate the tools are present but they
provide unexpected responses.

See if asdf has any way of setting up hooks to be called after installing
tools. Use these to automatically ask vim to install plugins.

Some vim plugins take flags that trigger dowloading/installing external binaries
so worth checking if any are missing from current vim config.

fzf can do all sorts of cool things, even to the extent of making small
interactive tools. Browsing go documentation is a prime example of this.

Try putting together a fzf command that shows and filters a list of all symbols
that go doc can be called with, and shows the actual documentation in the
preview window.

Bonus points if a keybinding can open docs in the browser.

• junegunn/fzf - Advanced fzf - examples

vim-go does too many great things for me to jettison it, but it would be
simpler to have all language server interaction happen through coc.nvim.

• Make sure no config is disabling coc.nvim for go files

• Adjust vim config to disable the vim-go integration with gopls

• Adjust coc.nvim config to interact with the gopls language server

• [joshrosso.com - Vim as a Go IDE](Vim as a Go IDE
  https://joshrosso.com/docs/2019/2019-04-24-vim-as-a-go-ide/)