krischik / vim-scripts

Automatically exported from code.google.com/p/vim-scripts
GNU General Public License v3.0
1 stars 0 forks source link

Mispelling #3

Closed GoogleCodeExporter closed 2 years ago

GoogleCodeExporter commented 9 years ago
The autoload script is named "rainbow_parenthsis" and the functions defined 
inside use the same spelling.  However, the variable 
"rainbow_parenthesis#active" uses the wrong spelling, causing an error.

Original issue reported on code.google.com by gra...@gmail.com on 21 Sep 2010 at 6:12

GoogleCodeExporter commented 9 years ago
yea, and why is this released without any proofreading.... so annoying. I just 
can't get it work.

Original comment by pen...@gmail.com on 18 Apr 2011 at 9:28

GoogleCodeExporter commented 9 years ago
As a quickie workaround, go into your "vimfiles" folder and open 
rainbow_parenthesis.vim. 

On line 68, open a line above it, and enter:
    let rainbow_parenthesis#active = 0

This just defines the variable, so that the next line executes successfully. 
Note : you can also remove all of that logic, and just have it run 
rainbowparenthesis#activate, because that's what it's going to do anyway. 

I got it working this way, but the parenthesis end up being highlighted in 
white when I have a black background, making it confusing on my eyes. I'll 
probably just find something else.

I've attached the edited, working file.

Original comment by Marzhal...@gmail.com on 25 Sep 2011 at 9:19

Attachments:

GoogleCodeExporter commented 9 years ago
Addendum to the above comment, in reference to the  parenthesis being 
highlighted:

in the same rainbow_parenthesis.vim file, lines 33-49 have the color 
definitions; remove all of the "guibg" options in order to have the backgrounds 
of the parenthesis remain the same as your theme's background color. Again, 
I've attached my fixed file.

I assume that if you remove the "ctermbg" options in those lines, it will have 
the same effect in the command line, but I haven't tried it.

Original comment by Marzhal...@gmail.com on 25 Sep 2011 at 9:33

Attachments:

krischik commented 2 years ago

Fixed in current version.