[GRASS-dev] [GRASS GIS] #3351: Update r.color manual

GRASS GRASS developer
1

#3351: Update r.color manual
------------------------------+-------------------------
Reporter: Nikos Alexandris | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone:
Component: Docs | Version: svn-trunk
Keywords: r.colors, rules | CPU: Unspecified
Platform: Unspecified |
------------------------------+-------------------------
In the manuals for `r.colors`, versions
[https://grass.osgeo.org/grass72/manuals/r.colors.html 7.2] and
[https://grass.osgeo.org/grass73/manuals/r.colors.html 7.3 ] it reads

   One can get a rough idea of the applicability of a colour table by
reading the corresponding rules file (`$GISBASE/etc/colors/<name>`).

Please update the path to `$GISBASE/lib/gis/colors/<name>`.

I guess this applies to all 7.x series?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3351&gt;
GRASS GIS <https://grass.osgeo.org>

2

#3351: Update r.color manual
-------------------------------+-----------------------------
  Reporter: Nikos Alexandris | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: normal | Milestone:
Component: Docs | Version: svn-trunk
Resolution: wontfix | Keywords: r.colors, rules
       CPU: Unspecified | Platform: Unspecified
-------------------------------+-----------------------------
Changes (by Nikos Alexandris):

* status: new => closed
* resolution: => wontfix

Comment:

I guess the users should indeed look in to the `$GISBASE/etc/colors/`
directory, not the source. Ticket does not apply.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3351#comment:1&gt;
GRASS GIS <https://grass.osgeo.org>

3

#3351: Update r.color manual
-------------------------------+-----------------------------
  Reporter: Nikos Alexandris | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: normal | Milestone:
Component: Docs | Version: svn-trunk
Resolution: wontfix | Keywords: r.colors, rules
       CPU: Unspecified | Platform: Unspecified
-------------------------------+-----------------------------

Comment (by neteler):

Doesn't r.colors.out do the job? Maybe we should highlight that.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3351#comment:2&gt;
GRASS GIS <https://grass.osgeo.org>

4

#3351: Update r.color manual
-------------------------------+-----------------------------
  Reporter: Nikos Alexandris | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: normal | Milestone:
Component: Docs | Version: svn-trunk
Resolution: wontfix | Keywords: r.colors, rules
       CPU: Unspecified | Platform: Unspecified
-------------------------------+-----------------------------

Comment (by Nikos Alexandris):

Would it make sense to merge down `r.colors.out` to `r.colors`?
The former's option `rules` could then be named `output` in the latter.

And, what about a simple flag that will print out the color rules in the
console, instead of a file?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3351#comment:3&gt;
GRASS GIS <https://grass.osgeo.org>

5

#3351: Update r.color manual
-------------------------------+-----------------------------
  Reporter: Nikos Alexandris | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: normal | Milestone: 7.4.1
Component: Docs | Version: svn-trunk
Resolution: wontfix | Keywords: r.colors, rules
       CPU: Unspecified | Platform: Unspecified
-------------------------------+-----------------------------
Changes (by neteler):

* milestone: => 7.4.1

Comment:

Replying to [comment:3 Nikos Alexandris]:
> Would it make sense to merge down `r.colors.out` to `r.colors`?
> The former's option `rules` could then be named `output` in the latter.

This would be a new ticket. Perhaps for G8?

> And, what about a simple flag that will print out the color rules in the
console, instead of a file?

... also part of the new ticket?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3351#comment:4&gt;
GRASS GIS <https://grass.osgeo.org>