Running :GoDoc makes my vim session block as it is not ran in the background. This might not be an issue for small codebases, where the blocking call is quick enough, but it causes frustration when using the command on larger codebases.

It would be great if :GoDoc runs in the background, without blocking my editor, similar to how the guru-related commands work (e.g. :GoReferrers)

It'd be a cool feature if coloured devicons worked out of the box. Perhaps include some colour maps for the stock shipped colorschemes and some popular 3rd party ones, a mechanism for users to define their own colour map for colorschemes, falling back to standard terminal colours for terminal vim and the actual colours as per filetype's official colour for GUI vim (e.g. Gulp's #cf4646 for the Gu

Please write a small note in the documentation on -

1. How to associate Yavide with a folder of existing source code?
2. How to make source code navigation working with the folder mentioned above?

Say, for instance, I have cloned Linux kernel source code and I want to start making changes to the source using Yavide.

Thanks & regards,
Sreenath

Currently if you're editing a docstring like this:

/// Foo<press enter>

You end up with:

/// Foo
//<cursor>

Ideally you would end up with 3 slashes on the second line. The Rust vim syntax files do this correctly, so I'm sure it's something that can be fixed

Would it be possible to display the files in a tree style structure, similar to let g:netrw_liststyle = 3. That's what I'm missing the most from netrw.

Keywords (such as FROM and RUN) should always be flush left.

I would expect that given this Dockerfile:

    FROM ubuntu
       RUN echo hi

That indenting it should result in:

FROM ubuntu
RUN echo hi

I think if the project description explained better what vim-gnupg actually does under the hood it would be easier for a new user to understand what kind of security guarantees vim-gnupg offers.

In my particular case, I would like to know if vim-gnupg decrypts the encrypted file to to memory or if it decrypts to a temporary file that gets stored on disk. If vim crashes while I am editing the file

Example:

let foo = (( 1+
            2)
          )
          let bar = 3;

I would expect this to be:

let foo = (( 1+
            2)
)
let bar = 3;

Highlighting breaks most lines after a template literal statement.

When I comment out that line the highlighting works correcty.

![Screenshot_2019-09-07_06-40-24](https://user-images.githubusercontent.com/2062154/64474473-f7f75280-d13a-11e9-9c41-5eb96b0beb

Steps:

1. Open file
2. Open Mundo
   - colors show up correctly
3. Close Mundo
4. :so $MYVIMRC
5. Open Mundo
   - Mundo is black and white

Investigate uses omniref for Ruby documentation, which was shut down a few months ago. I wanted to make a pull request but couldn't find an alternative with feature parity. Right now, though, it's broken.

I've had to disable roxma/vim-paste-easy because, with both it and pear-tree installed, if I type both an opener and a closer in less than a second (eg. function_with_no_arguments() or results = []), I wind up with a doubled closer.

I don't know enough about Vim's architecture and VimL to know which side should be responsible for fixing it, bu