[GRASS-user] Grass "stability"

GRASS GRASS user
1

Quick question: I have a colleague who is using 6.2.3 CYGWIN version of grass, and was wondering how people felt about that version (and platform's) stability vs. 6.3.0 (windows or *nix) or 6.2.3 *nix versions. I'm pretty convinced that 6.2.3 for cygwin is very moody and unstable, but I don't know if this statement is generally supported by the grass community. Thoughts?

--j

--
Jonathan A. Greenberg, PhD
Postdoctoral Scholar
Center for Spatial Technologies and Remote Sensing (CSTARS)
University of California, Davis
One Shields Avenue
The Barn, Room 250N
Davis, CA 95616
Cell: 415-794-5043
AIM: jgrn307, MSN: jgrn307@hotmail.com, Gchat: jgrn307

2

jonathan,

I've just returned to grass on cygwin a couple of weeks ago. Overall,
I think it's pretty much stable, a couple of quirks I encountered
though:

1. No cut and paste under startxwin.sh shell
2. Some of my simple scripts (for batch import of vector and raster)
are not working, both under the startxwin.sh and cygwin bash running
in Poderosa.

I don't think this is due to GRASS but more of the cygwin's bash
shell. I will report other things as I encounter it. Hope that helps
a bit.

cheers,
maning

On Fri, May 16, 2008 at 7:56 AM, Jonathan Greenberg
<greenberg@ucdavis.edu> wrote:

Quick question: I have a colleague who is using 6.2.3 CYGWIN version of
grass, and was wondering how people felt about that version (and platform's)
stability vs. 6.3.0 (windows or *nix) or 6.2.3 *nix versions. I'm pretty
convinced that 6.2.3 for cygwin is very moody and unstable, but I don't know
if this statement is generally supported by the grass community. Thoughts?

--j

--
Jonathan A. Greenberg, PhD
Postdoctoral Scholar
Center for Spatial Technologies and Remote Sensing (CSTARS)
University of California, Davis
One Shields Avenue
The Barn, Room 250N
Davis, CA 95616
Cell: 415-794-5043
AIM: jgrn307, MSN: jgrn307@hotmail.com, Gchat: jgrn307

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

3

maning sambale wrote:

I've just returned to grass on cygwin a couple of weeks ago. Overall,
I think it's pretty much stable, a couple of quirks I encountered
though:

1. No cut and paste under startxwin.sh shell

I'm not entirely clear what you mean by this. AFAICT, there are two
issues:

1. xterm doesn't use the clipboard by default, but the primary
selection. Consequently, you can't paste the selection with e.g.
Ctrl-V or Shift-Insert. This can be changed via the "Select to
Clipboard" option in the menu obtained from Ctrl+Button2 (the middle
button).

2. The X server needs to be started with the -clipboard switch to
enable synchronisation between the X clipboard and the Windows
clipboard.

2. Some of my simple scripts (for batch import of vector and raster)
are not working, both under the startxwin.sh and cygwin bash running
in Poderosa.

I don't think this is due to GRASS but more of the cygwin's bash
shell.

There isn't much different between Cygwin's bash and any other version
of bash.

Common causes of problems with shell scripts on Windows include:

1. Forgetting to put quotes around variables, i.e. "$variable". If you
omit the quotes, it will likely do the wrong thing if the value
contains spaces, and spaces in pathnames are far more common on
Windows than on Unix.

2. Incompatible programs in the path. E.g. if the System32 directory
is at the beginning of $PATH, "find" will refer to the Windows utility
of that name. Ditto for "sort".

--
Glynn Clements <glynn@gclements.plus.com>

4

Glynn,

Thank you for clearing things out. Will check and report results by
next week.

Have a nice weekend!

maning

1. xterm doesn't use the clipboard by default, but the primary
selection. Consequently, you can't paste the selection with e.g.
Ctrl-V or Shift-Insert. This can be changed via the "Select to
Clipboard" option in the menu obtained from Ctrl+Button2 (the middle
button).

2. The X server needs to be started with the -clipboard switch to
enable synchronisation between the X clipboard and the Windows
clipboard.

> 2. Some of my simple scripts (for batch import of vector and raster)
> are not working, both under the startxwin.sh and cygwin bash running
> in Poderosa.
>
> I don't think this is due to GRASS but more of the cygwin's bash
> shell.

There isn't much different between Cygwin's bash and any other version
of bash.

Common causes of problems with shell scripts on Windows include:

1. Forgetting to put quotes around variables, i.e. "$variable". If you
omit the quotes, it will likely do the wrong thing if the value
contains spaces, and spaces in pathnames are far more common on
Windows than on Unix.

2. Incompatible programs in the path. E.g. if the System32 directory
is at the beginning of $PATH, "find" will refer to the Windows utility
of that name. Ditto for "sort".