Hi,
Jürgen E. Fischer (jef) kindly updated GRASS in the OSGeo4W installer
to GRASS 6.4.0svn. This should enable more users to try out the
current state in order to get out 6.4.0RC4 quickly.
A series of stability fixes are included including fixes for Vista.
Please test and report.
Markus
Is it still under "advanced"?
Helena
On Mar 30, 2009, at 4:04 AM, Markus Neteler wrote:
Hi,
Jürgen E. Fischer (jef) kindly updated GRASS in the OSGeo4W installer
to GRASS 6.4.0svn. This should enable more users to try out the
current state in order to get out 6.4.0RC4 quickly.A series of stability fixes are included including fixes for Vista.
Please test and report.
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Mon, Mar 30, 2009 at 4:57 PM, Helena Mitasova <hmitaso@unity.ncsu.edu> wrote:
Is it still under "advanced"?
Yes, still in "advanced" in the OSGeo4W installer unless we get
positive feedback from the people testing it.
Markus
one more question -
is there any danger that the OSGeo4W install of of grass6.4 will screw up
Marco's grass6.3 install that people already have reliably running on their computers (both VISSTA and XP)?
(I have 4 versions of grass running on a linux computer but I am not sure about mswindows
and the installers),
Helena
On Mar 30, 2009, at 2:16 PM, Markus Neteler wrote:
On Mon, Mar 30, 2009 at 4:57 PM, Helena Mitasova <hmitaso@unity.ncsu.edu> wrote:
Is it still under "advanced"?
Yes, still in "advanced" in the OSGeo4W installer unless we get
positive feedback from the people testing it.Markus
I have both as well with no problems. The only overlap is the windows
PATH environment variable (and maybe the PYTHONPATH variable too), but
as long as windows has entries for both versions there is no problem.
-Colin
On Mon, Mar 30, 2009 at 3:10 PM, Milena Nowotarska <do.milenki@gmail.com> wrote:
Hi Helena,
I was running today both grass6.4.0RC3 and grass6.4.0svn at one time
and nothing alarming happened. Was not doing anything sophisticated,
just simply tasks. Will try to install it also on another computer,
where I have grass6.3. I use XP.Milena
2009/3/30 Helena Mitasova <hmitaso@unity.ncsu.edu>:
one more question -
is there any danger that the OSGeo4W install of of grass6.4 will screw up
Marco's grass6.3 install that people already have reliably running on their
computers (both VISSTA and XP)?
(I have 4 versions of grass running on a linux computer but I am not sure
about mswindows
and the installers),Helena
On Mar 30, 2009, at 2:16 PM, Markus Neteler wrote:
On Mon, Mar 30, 2009 at 4:57 PM, Helena Mitasova <hmitaso@unity.ncsu.edu>
wrote:Is it still under "advanced"?
Yes, still in "advanced" in the OSGeo4W installer unless we get
positive feedback from the people testing it.Markus
_______________________________________________
grass-windows mailing list
grass-windows@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-windows_______________________________________________
grass-windows mailing list
grass-windows@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-windows
Maxim Dubinin wrote:
Hi, great news on 6.4svn.
i18n is working!
Running Help\About system gives me this:
couldn't execute "C:OSGeo4Winwish.exe": no such file or directory
couldn't execute "C:OSGeo4Winwish.exe": no such file or directory
while executing
"exec C:\OSGeo4W\bin\wish.exe C:/OSGeo4W/apps/grass/grass-6.4.0svn/etc/gm/tksys.tcl --tcltk & "
(menu invoke)
The \b is being interpreted as ^H (backspace), and the other
backslashes are getting dropped.
This is due to the use of "subst" in the definition of descmenu in
gmmenu.tcl. This replaces all variable substitutions with their
values.
So, the command:
{ exec $env(GRASS_WISH) $env(GISBASE)/etc/gm/tksys.tcl --tcltk & }
gets expanded to:
{ exec C:\OSGeo4W\bin\wish.exe C:/OSGeo4W/apps/grass/grass-6.4.0svn/etc/gm/tksys.tcl --tcltk & }
The backslashes in the first argument (the wish path) are treated as
escape characters. \b is treated as ^H while \O and \w are treated as
O and w respectively.
Specifying GRASS_WISH using forward slashes will solve this problem,
but will cause problems if GRASS_WISH is used inside a Windows batch
file.
The path can be converted in Tcl with:
set env(GRASS_WISH) [file normalize $env(GRASS_WISH)]
But if the value is passed to the Windows command interpreter, it will
need to be converted back with "file nativename ...".
Alternatively, the variable expansion can be quoted, e.g.:
{ exec {$env(GRASS_WISH)} $env(GISBASE)/etc/gm/tksys.tcl --tcltk & }
There may be other cases where this is necessary. But this won't work
if the variable's value contains unmatched braces or ends in a
backslash.
The ideal solution would be to eliminate the "subst", but that would
mean:
1. Calling "subst" elsewhere, so that $tmenu and $keyctrl get
expanded.
2. Adding "global" statements for tmenu and keyctrl at those points.
3. Adding "global" statements within the commands for $env, $mon, and
$devnull.
Alternatively, descmenu could be constructed by using [list ...]
rather than braces. This will expand variables as the list is
constructed, and (unlike subst) will add braces and/or backslashes
where necessary.
Actually, using:
{[list exec $env(GRASS_WISH) $env(GISBASE)/etc/gm/tksys.tcl --tcltk &]}
while keeping the "subst" should work, and doesn't have problems when
the variable contains unmatched braces or a trailing backslash.
--
Glynn Clements <glynn@gclements.plus.com>