[GRASS-dev] table with the parser standard options

Dear devs,

I was not able to find a table in the GRASS manual pages with a
summary of all the default options as define in
parser_standard_options.c (lib/gis/parser_standard_options.c).
Therefore I wrote a python command line tool to extract them from the
source and print/write to a file in CSV/HTML format.
Probably I should use regexp but I'm not good with them...

The command line tool is attached.

Some usage example are:

$ python2 options.py -t lib/gis/parser_standard_options.c -f csv -o
stadard_options.csv

The command line should be able also to download the source file
directly from a link but it works only partially.

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

What do you think?

Pietro

(attachments)

options.py (5.4 KB)

On 1 July 2015 at 06:42, Pietro <peter.zamb@gmail.com> wrote:

Dear devs,

I was not able to find a table in the GRASS manual pages with a
summary of all the default options as define in
parser_standard_options.c (lib/gis/parser_standard_options.c).
Therefore I wrote a python command line tool to extract them from the
source and print/write to a file in CSV/HTML format.
Probably I should use regexp but I'm not good with them...

The command line tool is attached.

Some usage example are:

$ python2 options.py -t lib/gis/parser_standard_options.c -f csv -o
stadard_options.csv

The command line should be able also to download the source file
directly from a link but it works only partially.

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

if we want add the table in the manual docs (I'm really support this
idea) you should add this tool in the main code tools directory [0]

What do you think?

+1

Pietro

[0] https://trac.osgeo.org/grass/browser/grass/trunk/tools

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On 01/07/15 06:42, Pietro wrote:

Dear devs,

I was not able to find a table in the GRASS manual pages with a
summary of all the default options as define in
parser_standard_options.c (lib/gis/parser_standard_options.c).

There is http://grass.osgeo.org/programming7/parser__standard__options_8c.html#a1a5da9db1229a9bbc59d16ae84540bb8

which is referenced from the g.parser man page.

But I agree that a table like your's might be more helpful and that it should be accessible amongst the man pages.

Therefore I wrote a python command line tool to extract them from the
source and print/write to a file in CSV/HTML format.

Great, thanks !

May I just suggest the following small modification to make the html more readable:

--- options_orig.py 2015-07-01 11:57:54.146435072 +0200
+++ options.py 2015-07-01 11:57:30.234718383 +0200
@@ -105,7 +105,7 @@

      def html(self, endline='\n', indent=' '):
          """Return a HTML table with the options"""
- html = ["<table>"]
+ html = ["<table border=1>"]
          # write headers
          html.append(indent + "<tr>")
          html.append(indent * 2 + "<td>{0}</td>".format('option'))

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

Wouldn't it be better in tools/ directly in the source code ?

Moritz

Dear Luca and Moritz,

On Wed, Jul 1, 2015 at 11:58 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

May I just suggest the following small modification

ok, added.

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

Wouldn't it be better in tools/ directly in the source code ?

ok, committed in r65534.

Some examples:

{{{
$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv

$ tail parser_standard_options.csv
G_OPT_STR3DS_INPUT;;Name of the input space time raster3d
dataset;;old,str3ds,str3ds;input;name;;;;YES;TYPE_STRING
G_OPT_STR3DS_INPUTS;;Name of the input space time raster3d
datasets;;old,str3ds,str3ds;inputs;name;;YES;;YES;TYPE_STRING
G_OPT_STR3DS_OUTPUT;;Name of the output space time raster3d
dataset;;new,str3ds,str3ds;output;name;;;;YES;TYPE_STRING
G_OPT_STDS_TYPE;strds;Type of the input space time
dataset;;;type;name;;;strds,stvds,str3ds;NO;TYPE_STRING
G_OPT_MAP_INPUT;;Name of the input map;;old,map,map;map;name;;;;YES;TYPE_STRING
G_OPT_MAP_INPUTS;;Name of the input
maps;;old,map,map;maps;name;;YES;;YES;TYPE_STRING
G_OPT_MAP_TYPE;raster;Type of the input
map;;;type;name;;;raster,vector,raster_3d;NO;TYPE_STRING
G_OPT_T_TYPE;absolute;The temporal type of the space time
dataset;;;temporaltype;name;;;absolute,relative;NO;TYPE_STRING
G_OPT_T_WHERE;;Example: start_time > '2001-01-01
12:30:00';;;where;sql_query;WHERE conditions of SQL statement without
'where' keyword used in the temporal GIS framework;;;NO;TYPE_STRING
G_OPT_T_SAMPLE;start;The method to be used for sampling the input
dataset;;;sampling;name;;YES;start,during,overlap,contain,equal,follows,precedes;NO;TYPE_STRING

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f html -o
parser_standard_options.html

$ head parser_standard_options.html
<table border=1>
  <tr>
    <td>option</td>
    <td>answer</td>
    <td>description</td>
    <td>descriptions</td>
    <td>gisprompt</td>
    <td>key</td>
    <td>key_desc</td>
    <td>label</td>

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv -s Flg

$ tail parser_standard_options.csv
description;key
G_FLG_V_TABLE;Do not create attribute table;'t'
G_FLG_V_TOPO;Do not build topology;'b'
}}}

Best regards

Pietro

On 2 July 2015 at 09:49, Pietro <peter.zamb@gmail.com> wrote:

Dear Luca and Moritz,

Dear All,

On Wed, Jul 1, 2015 at 11:58 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

May I just suggest the following small modification

ok, added.

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

Wouldn't it be better in tools/ directly in the source code ?

ok, committed in r65534.

Some examples:

{{{
$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv

$ tail parser_standard_options.csv
G_OPT_STR3DS_INPUT;;Name of the input space time raster3d
dataset;;old,str3ds,str3ds;input;name;;;;YES;TYPE_STRING
G_OPT_STR3DS_INPUTS;;Name of the input space time raster3d
datasets;;old,str3ds,str3ds;inputs;name;;YES;;YES;TYPE_STRING
G_OPT_STR3DS_OUTPUT;;Name of the output space time raster3d
dataset;;new,str3ds,str3ds;output;name;;;;YES;TYPE_STRING
G_OPT_STDS_TYPE;strds;Type of the input space time
dataset;;;type;name;;;strds,stvds,str3ds;NO;TYPE_STRING
G_OPT_MAP_INPUT;;Name of the input map;;old,map,map;map;name;;;;YES;TYPE_STRING
G_OPT_MAP_INPUTS;;Name of the input
maps;;old,map,map;maps;name;;YES;;YES;TYPE_STRING
G_OPT_MAP_TYPE;raster;Type of the input
map;;;type;name;;;raster,vector,raster_3d;NO;TYPE_STRING
G_OPT_T_TYPE;absolute;The temporal type of the space time
dataset;;;temporaltype;name;;;absolute,relative;NO;TYPE_STRING
G_OPT_T_WHERE;;Example: start_time > '2001-01-01
12:30:00';;;where;sql_query;WHERE conditions of SQL statement without
'where' keyword used in the temporal GIS framework;;;NO;TYPE_STRING
G_OPT_T_SAMPLE;start;The method to be used for sampling the input
dataset;;;sampling;name;;YES;start,during,overlap,contain,equal,follows,precedes;NO;TYPE_STRING

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f html -o
parser_standard_options.html

$ head parser_standard_options.html
<table border=1>
  <tr>
    <td>option</td>
    <td>answer</td>
    <td>description</td>
    <td>descriptions</td>
    <td>gisprompt</td>
    <td>key</td>
    <td>key_desc</td>
    <td>label</td>

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv -s Flg

$ tail parser_standard_options.csv
description;key
G_FLG_V_TABLE;Do not create attribute table;'t'
G_FLG_V_TOPO;Do not build topology;'b'
}}}

In r66263 I improved the tools of Pietro (specially I added a new
GRASS output), moved it in man directory and added it to Makefile.
It now return a batter table, you should see it at this link [0] after
next manual compilation. Until now this page is not linked in any
other manual's page, let me know where do you think should be
better...

Best regards

Pietro

Regards from Seoul

[0] https://grass.osgeo.org/grass71/manuals/parser_standard_options.html

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

Hi Luca,

2015-09-19 6:37 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:

In r66263 I improved the tools of Pietro (specially I added a new
GRASS output), moved it in man directory and added it to Makefile.
It now return a batter table, you should see it at this link [0] after
next manual compilation. Until now this page is not linked in any
other manual's page, let me know where do you think should be
better...

thanks, unfortunately travis has problem with that

GISBASE="/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu"
ARCH="x86_64-pc-linux-gnu"
ARCH_DISTDIR="/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu"
VERSION_NUMBER=7.1.svn VERSION_DATE=2015 python
./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o /home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu/docs/html/parser_standard_options.html
-p 'id="opts_table" class="scroolTable"'
Traceback (most recent call last):
  File "./parser_standard_options.py", line 157, in <module>
    args = parser.parse_args()
  File "/usr/lib/python2.7/argparse.py", line 1688, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python2.7/argparse.py", line 1710, in parse_known_args
    default = self._get_value(action, default)
  File "/usr/lib/python2.7/argparse.py", line 2239, in _get_value
    raise ArgumentError(action, msg)
argparse.ArgumentError: argument -t/--text: can't open '': [Errno 2]
No such file or directory: ''
make[3]: *** [/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu/docs/html/parser_standard_options.html]
Error 1

Locally it's compiled fine.

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Il 19/set/2015 10:42, “Martin Landa” <landa.martin@gmail.com> ha scritto:

Hi Luca,

Hi Martin,

thanks, unfortunately travis has problem with that

GISBASE=“/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu”
ARCH=“x86_64-pc-linux-gnu”
ARCH_DISTDIR=“/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu”
VERSION_NUMBER=7.1.svn VERSION_DATE=2015 python
./parser_standard_options.py -t …/lib/gis/parser_standard_options.c
-f grass -o /home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu/docs/html/parser_standard_options.html
-p ‘id=“opts_table” class=“scroolTable”’
Traceback (most recent call last):
File “./parser_standard_options.py”, line 157, in
args = parser.parse_args()
File “/usr/lib/python2.7/argparse.py”, line 1688, in parse_args
args, argv = self.parse_known_args(args, namespace)
File “/usr/lib/python2.7/argparse.py”, line 1710, in parse_known_args
default = self._get_value(action, default)
File “/usr/lib/python2.7/argparse.py”, line 2239, in _get_value
raise ArgumentError(action, msg)
argparse.ArgumentError: argument -t/–text: can’t open ‘’: [Errno 2]
No such file or directory: ‘’
make[3]: *** [/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu/docs/html/parser_standard_options.html]
Error 1

Locally it’s compiled fine.

Yes I saw it, I don’t know what’s wrong there, Ivan do you have any idea?

Anyone has the same problem?

Martin

Ciao
Luca

2015-09-19 10:51 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:

GISBASE="/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu"
ARCH="x86_64-pc-linux-gnu"

ARCH_DISTDIR="/home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu"
VERSION_NUMBER=7.1.svn VERSION_DATE=2015 python
./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o /home/travis/build/GRASS-GIS/grass-ci/dist.x86_64-pc-linux-gnu/docs/html/parser_standard_options.html

-p 'id="opts_table" class="scroolTable"'

I check locally compilation log and found:

GISBASE="/opt/src/grass_trunk/dist.x86_64-unknown-linux-gnu"
ARCH="x86_64-unknown-linux-gnu"
ARCH_DISTDIR="/opt/src/grass_trunk/dist.x86_64-unknown-linux-gnu"
VERSION_NUMBER=7.1.svn VERSION_DATE=2015 python
./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o /opt/src/grass_trunk/dist.x86_64-unknown-linux-gnu/docs/html/parser_standard_options.html
-p 'id="opts_table" class="scroolTable"'

So nothing special, my Python is

Python 2.7.10 (default, Sep 13 2015, 20:30:50)
[GCC 5.2.1 20150911] on linux2

Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Hi,

2015-09-19 10:51 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:

./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o

[...]

  File "/usr/lib/python2.7/argparse.py", line 2239, in _get_value
    raise ArgumentError(action, msg)
argparse.ArgumentError: argument -t/--text: can't open '': [Errno 2]

it seems to be problem with relative path. Luca, could you change it
to absolute path?

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Hi,

2015-09-19 11:11 GMT+02:00 Martin Landa <landa.martin@gmail.com>:

probably I overlooked that, but are you planning to link this page
somewhere, eg. in g.parser manual page?

Thaks, Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

On 19/09/15 06:37, Luca Delucchi wrote:

On 2 July 2015 at 09:49, Pietro <peter.zamb@gmail.com> wrote:

Dear Luca and Moritz,

Dear All,

On Wed, Jul 1, 2015 at 11:58 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

May I just suggest the following small modification

ok, added.

I believe we should add the generated table somewhere in the manual docs.
Should I add this python script to grass_addons/tools?

Wouldn't it be better in tools/ directly in the source code ?

ok, committed in r65534.

Some examples:

{{{
$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv

$ tail parser_standard_options.csv
G_OPT_STR3DS_INPUT;;Name of the input space time raster3d
dataset;;old,str3ds,str3ds;input;name;;;;YES;TYPE_STRING
G_OPT_STR3DS_INPUTS;;Name of the input space time raster3d
datasets;;old,str3ds,str3ds;inputs;name;;YES;;YES;TYPE_STRING
G_OPT_STR3DS_OUTPUT;;Name of the output space time raster3d
dataset;;new,str3ds,str3ds;output;name;;;;YES;TYPE_STRING
G_OPT_STDS_TYPE;strds;Type of the input space time
dataset;;;type;name;;;strds,stvds,str3ds;NO;TYPE_STRING
G_OPT_MAP_INPUT;;Name of the input map;;old,map,map;map;name;;;;YES;TYPE_STRING
G_OPT_MAP_INPUTS;;Name of the input
maps;;old,map,map;maps;name;;YES;;YES;TYPE_STRING
G_OPT_MAP_TYPE;raster;Type of the input
map;;;type;name;;;raster,vector,raster_3d;NO;TYPE_STRING
G_OPT_T_TYPE;absolute;The temporal type of the space time
dataset;;;temporaltype;name;;;absolute,relative;NO;TYPE_STRING
G_OPT_T_WHERE;;Example: start_time > '2001-01-01
12:30:00';;;where;sql_query;WHERE conditions of SQL statement without
'where' keyword used in the temporal GIS framework;;;NO;TYPE_STRING
G_OPT_T_SAMPLE;start;The method to be used for sampling the input
dataset;;;sampling;name;;YES;start,during,overlap,contain,equal,follows,precedes;NO;TYPE_STRING

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f html -o
parser_standard_options.html

$ head parser_standard_options.html
<table border=1>
   <tr>
     <td>option</td>
     <td>answer</td>
     <td>description</td>
     <td>descriptions</td>
     <td>gisprompt</td>
     <td>key</td>
     <td>key_desc</td>
     <td>label</td>

$ python2 tools/parser_standard_options.py -t
lib/gis/parser_standard_options.c -f csv -o
parser_standard_options.csv -s Flg

$ tail parser_standard_options.csv
description;key
G_FLG_V_TABLE;Do not create attribute table;'t'
G_FLG_V_TOPO;Do not build topology;'b'
}}}

In r66263 I improved the tools of Pietro (specially I added a new
GRASS output), moved it in man directory and added it to Makefile.
It now return a batter table, you should see it at this link [0] after
next manual compilation. Until now this page is not linked in any
other manual's page, let me know where do you think should be
better...

Great job, thanks !

It should certainly be linked to from the g.parser man page (in replacement of the link to the programmer's manual).

Maybe there could also be a direct link in the "Miscellaneous & Variables" section ?

Moritz

Hi,

in r66271 I have submitted an attempt to fix the Travis issue.

On Mon, Sep 21, 2015 at 1:11 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Great job, thanks !

It should certainly be linked to from the g.parser man page (in replacement
of the link to the programmer's manual).

Maybe there could also be a direct link in the "Miscellaneous & Variables"
section ?

Yes, would be nice.

Markus

On 19 September 2015 at 11:11, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2015-09-19 10:51 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:

./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o

[...]

  File "/usr/lib/python2.7/argparse.py", line 2239, in _get_value
    raise ArgumentError(action, msg)
argparse.ArgumentError: argument -t/--text: can't open '': [Errno 2]

it seems to be problem with relative path. Luca, could you change it
to absolute path?

tried in r66299, I hope this is fixing the problem in travis ci. Let's see

Martin

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On 21 September 2015 at 19:02, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

Hi,

in r66271 I have submitted an attempt to fix the Travis issue.

On Mon, Sep 21, 2015 at 1:11 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Great job, thanks !

It should certainly be linked to from the g.parser man page (in replacement
of the link to the programmer's manual).

Maybe there could also be a direct link in the "Miscellaneous & Variables"
section ?

Yes, would be nice.

ok, I will add in g.parser and in the "Miscellaneous & Variables" box

Markus

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On 23 September 2015 at 09:26, Luca Delucchi <lucadeluge@gmail.com> wrote:

On 19 September 2015 at 11:11, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2015-09-19 10:51 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:

./parser_standard_options.py -t ../lib/gis/parser_standard_options.c
-f grass -o

[...]

  File "/usr/lib/python2.7/argparse.py", line 2239, in _get_value
    raise ArgumentError(action, msg)
argparse.ArgumentError: argument -t/--text: can't open '': [Errno 2]

it seems to be problem with relative path. Luca, could you change it
to absolute path?

tried in r66299, I hope this is fixing the problem in travis ci. Let's see

absolute path didn't work, I also tried to protect the values of the
options but it didn't work too.
The error seems the the option -t/--text is empty, could be a problem
of argparse version?

Is there any way to contact the Travis-CI guys for some support?

I have no other ideas how to fix this problem, specially because it
seems related only to Travis....

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On Wed, Sep 23, 2015 at 9:57 AM, Luca Delucchi <lucadeluge@gmail.com> wrote:

absolute path didn't work, I also tried to protect the values of the
options but it didn't work too.
The error seems the the option -t/--text is empty, could be a problem
of argparse version?

Suggestion: add an "echo ..." there to print the actual line into the
log in order to better understand the issue?

Markus

On 23 September 2015 at 10:16, Markus Neteler <neteler@osgeo.org> wrote:

Suggestion: add an "echo ..." there to print the actual line into the
log in order to better understand the issue?

ok, this is the diff, it is correct?

Index: Makefile

--- Makefile (revision 66300)
+++ Makefile (working copy)
@@ -87,6 +87,8 @@
        VERSION_NUMBER=$(GRASS_VERSION_NUMBER)
VERSION_DATE=$(GRASS_VERSION_DATE) \
        $(PYTHON) ./parser_standard_options.py -t
"$(GRASS_HOME)/lib/gis/parser_standard_options.c" \
        -f "grass" -o "$(HTMLDIR)/parser_standard_options.html" -p
'id="opts_table" class="scroolTable"'
+ @echo "****DEBUG****" $(PYTHON) ./parser_standard_options.py
-t "$(GRASS_HOME)/lib/gis/parser_standard_options.c" \
+ -f "grass" -o "$(HTMLDIR)/parser_standard_options.html" -p
'id="opts_table" class="scroolTable"'
endef

$(HTMLDIR)/topics.html: $(ALL_HTML)

Markus

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

On Wed, Sep 23, 2015 at 10:22 AM, Luca Delucchi <lucadeluge@gmail.com> wrote:

On 23 September 2015 at 10:16, Markus Neteler <neteler@osgeo.org> wrote:

Suggestion: add an "echo ..." there to print the actual line into the
log in order to better understand the issue?

ok, this is the diff, it is correct?

Index: Makefile

--- Makefile (revision 66300)
+++ Makefile (working copy)
@@ -87,6 +87,8 @@
        VERSION_NUMBER=$(GRASS_VERSION_NUMBER)
VERSION_DATE=$(GRASS_VERSION_DATE) \
        $(PYTHON) ./parser_standard_options.py -t
"$(GRASS_HOME)/lib/gis/parser_standard_options.c" \
        -f "grass" -o "$(HTMLDIR)/parser_standard_options.html" -p
'id="opts_table" class="scroolTable"'
+ @echo "****DEBUG****" $(PYTHON) ./parser_standard_options.py
-t "$(GRASS_HOME)/lib/gis/parser_standard_options.c" \
+ -f "grass" -o "$(HTMLDIR)/parser_standard_options.html" -p
'id="opts_table" class="scroolTable"'
endef

I don't think it is correct (the " are not right I think) but you need
to send it either as attachment or HTML courier font formatted text...

thanks
Markus

Hi,

2015-09-24 11:56 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

travis issue seems to be fixed in r66323 (thanks to Ivan Mincik) [1]. Ma

[1] https://travis-ci.org/GRASS-GIS/grass-ci/builds/81968450

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

On 24 September 2015 at 16:10, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

Hi,

travis issue seems to be fixed in r66323 (thanks to Ivan Mincik) [1]. Ma

[1] https://travis-ci.org/GRASS-GIS/grass-ci/builds/81968450

Yes, I saw it... is there also an explanation about the fix?

Thanks a lot

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org