Huidae Cho

Please add a test script.

**Method** 1. RGB => HSL 2. Sort areas by L in an ascending order 3. For each area, calculate the cumulative area (`sum_area`) and probability (`L`) by `sum_area / total_area`...

In fact, these two commands don't work either: ```bash v.colors map=censusblk_swwake use=attr column=TOTAL_POP color=blues -g v.colors map=censusblk_swwake use=attr column=TOTAL_POP color=blues -a ``` because `Rast_log_colors()` and `Rast_abs_log_colors()` interpolates categories, which doesn't...

> > > This does not work correctly on my Mac. I just cloned and complied it within the past hour. I tested it with the NC census block data....

> I see. I think this PR needs some (a lot of?) work. It gets tricky to implement histogram equalization for vector features. BTW, have you tried `-a` or `-g`?...

Hi @wenzeslaus. I'm against this PR. I think, with only one option for an RGB column, the current behavior (same color for both area and boundary) is more expected. Also,...

I did a little test. By default, the current _d.vect_ only draws points, lines, areas, and faces **from the command line**. From the GUI, it draws boundaries as well. I...

@wenzeslaus Is this PR still relevant? I cannot reproduce this issue. From the NC sample mapset, ```bash g.copy vect=boundary_county,tmp --o v.db.addcolumn map=tmp col="rgb_color varchar(50)" v.db.update tmp col=rgb_color querycol="abs(random()%255) || ':'...

> > > I was concerned with color table meaning the color rules saved with the map (`$MAPSET_PATH/vector/country_boundaries/colr`) which I created with: > > ``` > v.colors map=country_boundaries color=inferno >...

> (test e.g. by setting line `width` high I would say that *is* a bug. `d.vect` should not draw thick boundaries when no `type=boundary` is specified. I mean for `type=area`...