#533 closed defect (wontfix)
Unusable shell for wingrass through osgeo4w
| Reported by: | cnielsen | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 6.4.0 |
| Component: | Installation | Version: | unspecified |
| Keywords: | Cc: | ||
| CPU: | x86-32 | Platform: | MSWindows XP |
Description
After installing grass using osgeo4w, and then using the desktop icon to start grass, grass starts but the console is not available to type in. It's just blank and typing or hitting enter does nothing. (osgeo4w trac?)
Change History (3)
comment:1 by , 16 years ago
| CPU: | Unspecified → x86-32 |
|---|---|
| Platform: | Unspecified → MSWindows XP |
follow-up: 3 comment:2 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , 15 years ago
Replying to cnielsen:
Apparently the console was not meant to be used and is only there for error messages. The cmd box at the bottom of the main window, or starting grass through msys are work-arounds.
No, I think that's a misreading of it. The console is there for more that just error messages and is meant to be used if present. I guess it is up to the packager to decide if to include it or not. During the debugging era of WinGrass I'd suggest to include it, but that's just my 1c.
I believe jef posted a patch to fix this for tcl/tk over on the osgeo4w trac site (# 83), just applied in 6.5svn.
https://trac.osgeo.org/osgeo4w/wiki/pkg-grass#OpenTickets
Hamish
Apparently the console was not meant to be used and is only there for error messages. The cmd box at the bottom of the main window, or starting grass through msys are work-arounds.