After 'g.gisenv set=DEBUG=3' the menu entry corresponding to v.db.connect (vector -> vector<->database connection -> set connection) provokes an error.
No more error after setting DEBUG back with g.gisenv set=DEBUG.
Don't know if this also concerns other modules.
Moritz
I'm baffled about this.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
From: Moritz Lennert <mlennert@club.worldonline.be>
Date: Tue, 03 Oct 2006 17:20:55 +0200
To: Michael Barton <michael.barton@asu.edu>
Cc: Grass Developers List <grass-dev@grass.itc.it>
Subject: [bug report] gis.m: error when launching v.db.connect from menu with
DEBUG set to 3After 'g.gisenv set=DEBUG=3' the menu entry corresponding to
v.db.connect (vector -> vector<->database connection -> set connection)
provokes an error.No more error after setting DEBUG back with g.gisenv set=DEBUG.
Don't know if this also concerns other modules.
Moritz
Moritz Lennert wrote:
After 'g.gisenv set=DEBUG=3' the menu entry corresponding to
v.db.connect (vector -> vector<->database connection -> set
connection) provokes an error.No more error after setting DEBUG back with g.gisenv set=DEBUG.
Don't know if this also concerns other modules.
could this (again) be a case of a huge flood of stderr messages
overwhelming TclTk?
Hamish