[GRASS-dev] r.rgb: syntax error, unexpected $end, expecting VARNAME or NAME or STRING

[Markus Neteler]

On Wed, Mar 23, 2016 at 3:50 PM, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> On Wed, Mar 23, 2016 at 6:44 AM, Markus Neteler <neteler at osgeo.org> wrote:
>>
>> On Tue, Mar 22, 2016 at 10:37 PM, Markus Metz
>> <markus.metz.giswork at gmail.com> wrote:
>> > On Fri, Mar 18, 2016 at 3:10 PM, Markus Neteler <neteler at osgeo.org>
>> > wrote:
>> ...
>> >>>> GRASS 7.1.svn (nc_spm_08_grass7): > r.rgb input=elevation
>> ...
>> > Is there any reason why this should not work? According to the manual
>> > it should work.
>> >
>> > If neither red or green or blue are given, r.rgb could use
>> > red=${input}.r
>> > green=${input}.g
>> > blue=${input}.b
>>
>> Yes, this would exactly be the user's expectation (at least mine as a
>> user) who has even read the manual :)
>
>
> I though you expected that the names are not generated inside the module
> since you changed the manual according to my commit (r68072) and backported
> both commits.

Yes, to get rid of this behaviour:

GRASS 7.1.svn (nc_spm_08_grass7): > r.rgb input=elevation
syntax error, unexpected $end, expecting VARNAME or NAME or STRING
Parse error
ERROR: parse error
ERROR: An error occurred while running r.mapcalc

Still the requirement to write 3 times almost the same output name is not ideal.

> I like the current state. Perhaps not so convenient when advanced users work
> in the command line but in all other cases it requires you to be explicit,
> thus better for beginners (who don't have to guess the new name) and the GUI
> (wxGUI can automatically show the new maps only when they are specified in
> the command line).

I see. Too bad that I also like the command line :-)

Markus