This related to issue #231. It would be useful to have an option to highlight variables that are escaping in the heap.

words can not be shown complete, origin words are followed:

OS: Debian 3.16.43-2+deb8u3 (2017-08-15) x86_64 GNU/Linux
Vim : VIM - Vi IMproved 7.4

how to fix this bug

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

It would be nice if the highlighting distinguished between regular comments // and /* ... */ and comments containing documentation: /// and /** ... */. The former keeping the form of traditional comments with the later having a different formatting as for "document string". The formatting might be used the same as for strings (would keep visual consistency with languages such as Python). T

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

The grammar for RegExp literals in ES6 allows / to appear without a preceding \ in character class expressions (see RegularExpressionClassChar in the grammar). However, vim-es6 highlights such expressions incorrectly. For example, in the following:

/foo[/]bar/

vim-es6 does not high

Say we have a function foo(). Somewhere in the codebase (e.g. some_file.cpp) a multi-line comment references it:

...
/**
 * This function wraps foo()
 */
Bar()
...

And when I try to find the definition for foo() I see some_file.cpp:42 * This function wraps foo() listed. Obviously this is undesired.

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