The code runs a DOM query to find the elements configured through the keys of the `styles` object on the parameters/configuration, then for each of those selectors, calculates a rect relative to the size of the canvas, and paints a colored rectangle for each of those elems (using the color coming form the values on styles). 
This kinda solves it:
:hi Folded ctermfg=239
:hi Folded ctermbg=233
First of all, I prefer to have less on my screen, not more. I believe that the less visual clutter you have on the screen the better you feel and the more productive you are.
Second, activating tagbar adds a bar on the right. That means my code window will shrink. But my code window is exactly the size I like it.
Third, I would have to trust those many thousands of lines of code by "someone from the internet".
Completely agree on this one. I'd probably prefer it if you can toggle between tagbar's view and your code (there may or may not be a way to do that, I didn't look at the docs).
> Third, I would have to trust those many thousands of lines of code by "someone from the internet".
This is true, but then again, you're already trusting vim, Linux and millions of lines of code all around you ;) It all comes down to trade-offs at the end of the day.
I don't see how this is useful. It reminds me of the redundant scroll indicators on the top of some websites.
Not sure if you have to be the author of the thing, to use the "Show HN: " title tag... but it would be helpful to people browsing...
I was wondering if something like this existed the other day, and I was excited to see this / share it, but I didn't want to put people under the false impression that I'd written this library.