Helmut Kudrnovsky wrote: > > >the desktop-shortcut to start WinGrass7 with Msys is actuallay following: > > > > > >"C:\Program Files\GRASS-70-SVN\msys\msys.bat" "/grass/bin/grass70 > > >-wxpython" > > >(http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Installer.nsi#L624) > > > > > >I've tried a little different approaches to launch WinGrass7 with a > > >msys-command-line , but no success at > > >the moment. > > > > >> maybe any hints? > > > >Create a batch file which sets SHELL to the full Windows path to MSys' > >sh.exe then runs grass70.py > > now I'm a little bit confused, because the installed C:\Program > Files\GRASS-70-SVN\grass70.bat already > does this: > > "[...] > rem Path to the shell command > set GRASS_SH=%GISBASE%\msys\bin\sh.exe > [...] > %GRASS_PYTHON% "%GISBASE%\grass70.py" %* > "
That doesn't set SHELL, which is what grass70.py uses to decide which shell to run. GRASS_SH is the program used for running shell scripts. > in my original post > (http://lists.osgeo.org/pipermail/grass-dev/2010-April/049998.html): > > "in this windows-console you can start - if you want within a Grass7-session > - python or a shell > (in this shell you have access to sed, awk, ...) and can use also all > windows-commandline-tools." > > so therefore I've suggested to remove the "WinGrass7 with msys-shortcut" > because there is already a shell accessible. There should be separate shortcuts for running GRASS with cmd.exe and with sh.exe. -- Glynn Clements <[email protected]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
