[GRASS-SVN] r69669 - grass/trunk/display/d.linegraph

[svn_grass at osgeo.org]

Author: wenzeslaus
Date: 2016-10-03 16:50:16 -0700 (Mon, 03 Oct 2016)
New Revision: 69669

Modified:
   grass/trunk/display/d.linegraph/d.linegraph.html
   grass/trunk/display/d.linegraph/main.c
Log:
d.linegraph: fix typo in r69648 and include todos

Modified: grass/trunk/display/d.linegraph/d.linegraph.html
===================================================================
--- grass/trunk/display/d.linegraph/d.linegraph.html	2016-10-03 23:39:22 UTC (rev 69668)
+++ grass/trunk/display/d.linegraph/d.linegraph.html	2016-10-03 23:50:16 UTC (rev 69669)
@@ -23,7 +23,7 @@
 <h3>File inputs</h3>
 
 If the <b>directory</b> option is provided, the paths to files can (and
-should) be only relative paths to these files. WHile this is not recommended
+should) be only relative paths to these files. While this is not recommended
 for scripting, it can be advantageous when typing the paths
 manually. For example when all files are stored in the directory
 <tt>/home/john/data</tt>, the user can provide the following in the command
@@ -98,7 +98,7 @@
 <p>
 The way the program locates and labels tic marks is less than perfect:
 <br>
-1) although distances between Y tics is proportional to the value, they are
+1) although distances between Y tics are proportional to the value, they are
 not proportional on the X axis;
 <br>
 2) decimal values between -1 and 1 can be printed on the X axis, but not

Modified: grass/trunk/display/d.linegraph/main.c
===================================================================
--- grass/trunk/display/d.linegraph/main.c	2016-10-03 23:39:22 UTC (rev 69668)
+++ grass/trunk/display/d.linegraph/main.c	2016-10-03 23:50:16 UTC (rev 69669)
@@ -217,6 +217,7 @@
     if (G_parser(argc, argv))
 	exit(EXIT_FAILURE);
 
+    /* TODO: put this to variables, and avoid -Wsign-compare */
     for (i = 0; i < 3; i++) {
 	for (j = 0; j < strlen(title[i]->answer); j++)
 	    if (title[i]->answer[j] == '_')
@@ -263,6 +264,7 @@
 
     title_color = D_translate_color(t_color_opt->answer);
 
+    /* TODO: use parser for the following and avoid -Wsign-compare */
     /* I had an argument with the parser, and couldn't get a neat list of
        the input colors as I thought I should. I did a quick hack to get
        my list from the answer var, which gives us the colors input