Hi, just tested following here with [1]:
- OSGeo4W-winGRASS-console: starting bash: C:\>bash GRASS 7.4.2> - to see if env var are still there, e.g. GRASS 7.4.2> echo $GRASS_PYTHON C:\OSGEO4~1\bin\python.exe the variables set beforehand are still there - starting a binary grass module there: GRASS 7.4.2> g.region --help Manages the boundary definitions for the geographic region. Usage: g.region [-dsplectwmn3bgfau] [region=name] [raster=name[,name,...]] [raster_3d=name] [vector=name[,name,...]] [n=value] [s=value] [e=value] [w=value] [t=value] [b=value] [rows=value] [cols=value] or GRASS 7.4.2> g.region just starts the GUI - try to start a script module, e.g. r.reclass.area GRASS 7.4.2> r.reclass.area.bat /c/OSGEO4~1/apps/grass/grass-7.4.2/bin/r.reclass.area.bat: line 1: @%GRASS_PYTHON%: command not found it seems %GRASS_PYTHON%, or in the sense of bash $GRASS_PYTHON, seems not to be expanded while running bash. any idea how to get the script modules working? [1] System Info GRASS version: 7.4.2 GRASS SVN revision: r73591 Build date: 2018-10-23 Build platform: x86_64-w64-mingw32 GDAL: 2.3.2 PROJ.4: 5.2.0 GEOS: 3.7.0 SQLite: 3.17.0 Python: 2.7.14 wxPython: 2.8.12.1 Platform: Windows-10-10.0.17134 (OSGeo4W) ----- best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
