On Mon, 2003-10-13 at 12:50, Felix Kühling wrote:
On Sun, 12 Oct 2003 22:46:38 +0200 Michel Dänzer <[EMAIL PROTECTED]> wrote:
On Sun, 2003-10-12 at 00:15, Felix Kühling wrote:
On Sat, 11 Oct 2003 01:49:27 +0200 Michel Dänzer <[EMAIL PROTECTED]> wrote:
This means that most environment variables stop working [...]
How hard do you think it would be to allow options to be overridden by environment variables for debugging, along the lines of
tcl_mode=0 torcs
It would be quite simple. But I think we should not allow this in
production builds (e.g. snapshots ;-).
Why not? What if the warnings were always printed?
IIRC not allowing environment variables to change the configuration was
supposed to avoid unreproducible bugs. Always printing warnings to
stderr may be a good compromise though.
IMHO it is, but I'm very interested in other opinions.
IMHO changing an option in driconf is as fast as or faster than typing an environment variable.
When trying different values for a setting, without environment variables I have to
* switch to the driconf window (or the editor with ~/.drirc open) * change the setting * save the settings * switch back to the terminal * start the app
This would be a real pain during development...
whereas with environment variables, I only have to
* go back in the shell history * change the setting * press enter
and I don't have to remember what the settings were before.
I would definitely find this less painful...
Keith
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
