[GRASS-dev] GRASS extensions/addons mismatch

[Michael Barton]

No problem. At least I know I'm not crazy. I did try it from the command line before posting and it said 'can't be found'. Doesn't exist in the bin or scripts directories either of course.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 	480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu











On Dec 21, 2011, at 8:26 AM, Moritz Lennert wrote:

> On 21/12/11 14:05, Martin Landa wrote:
>> Hi,
>> 
>> 2011/12/21 Moritz Lennert<mlennert at club.worldonline.be>:
>>>> 1) I have been testing with the bash script in GRASS 6.4svn. At least
>>>> I'm pretty sure that is what I've been doing. It certainly looks like
>>>> that is what I get if I press "go to command dialog" from the
>>>> g.extension wrapper gui (is that what you are referring to as
>>>> g.extension.py??).
>> 
>> yes, it will launch g.extension.py.
> 
> Sorry for my wrong response. I was looking at an out-of-date version of 
> grass6.4svn.
> 
> Moritz