It looks like "options" or whatever the allowed values are called.

It looks like "options" or whatever the allowed values are called.

They are passed to the module parser and G__split_gisprompt() assumes the option value is correct:

During compilation this is triggered by documentation generation (calling parser html|md).

I don't doubt this fails. What I meant is that there is options and the current values look like the value to set there.

example: https://github.com/OSGeo/grass/blob/main/raster/r.viewshed/main.cpp#L509
doc: https://grass.osgeo.org/programming8/structOption.html#aaf64185e77299e332f9fcb4880a0507b

I don't doubt this fails. What I meant is that there is options and the current values look like the value to set there.

example: https://github.com/OSGeo/grass/blob/main/raster/r.viewshed/main.cpp#L509 doc: https://grass.osgeo.org/programming8/structOption.html#aaf64185e77299e332f9fcb4880a0507b

Aha, now I see what you mean, you suggest something like:

- # % gisprompt: -90-90
+ # % options: -90-90

Yes!

Now I changed to use "options".