firejump / vscode-frame-rainbow Goto Github PK

There is a bug that when a user clicks on a line close to the end it will not position the cursor at the end of the line, but one char before.

I like the concept very much, however I am overwhelmed by the eye clutter it introduces.

Code like this can result in a lot of color changes in rapid succession, particularly the short if else statements.

I don't know if it would be a benefit or not but I suspect that only coloring the "current" block and maybe the one wrapping it would be a good idea. something like the current builtin bracket marker line that's on the side.

First, this extension is already very helpful.

A further improvement which would greatly help when working with e.g. LISP files would be:

• colorize background of the bracket pairs on the same line, similar to what
• if the brackets are indented inconsistently, switch colorization not by indent depth but by bracket depth

example:

here i'd expect the (if on line 102 to be colorized in violet not cyan, both (starts-with ... and (net-send-get-result on lines 103-104 to be colored cyan, and (append "." lne) to be colored orange

Hello, great idea and nice extension!

Is there any way to limit the depth? for example only to take 2 levels (after parenthesis or brackets) inside and paint all the next levels on the same color than parent.
In my case I have a lot of levels but I don't want to see every level. I just want 2 or 3 levels to identify where my function ends easily.

Thanks for your attention.
Regards.

hey i've just discover this tool and it's very nice

this is exactly what I was looking for although I only knew indent-rainbow before

it feel very strange to me to not have the root function with a color frame

Here's a video demonstrating the problem. The problem goes away when I switch off this extension.

When you click on the very right of an expression sorrounded by parenthesis, the cursor keeps inside of parenthesis instead of outside

This is the actual behavior

This is what should be

When I disable this extensión I have the right behavior