To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54275
------- Additional comments from [EMAIL PROTECTED] Thu Apr 27 12:10:41 -0700 2006 ------- So - wrt. documenting environment variables, see what I started in this area turned into: http://wiki.services.openoffice.org/wiki/Environment_Variables - still a work in progress for sure, but something. > The configuration should be used to control features. If I set this in the configuration, I will be lumbered with it for all invocations, and (inevitably) forget to turn it off - rather than being able to run in a debug environment with this on temporarily. > Yes there's other usage of environment variables but this should only be > the case if this is the only way for something that's used during > bootstrapping or similar and just controls a technical feature. Ok - so *perhaps* what I understand by this is that you want a user-visible way to also disable auto-recovery, and you don't want users using this for it ? - if so, then I guess I can put some effort into writing that feature too - although, honestly I can't imagine why it would be useful. Wrt. usage of env. vars - cf. the link above there are a (metric) bus-load of them with explicit debugging/developer effects. > The right way to introduce an environment variable would be by using > "#if OSL_DEBUG_LEVEL > 1" because the solution is for debugging purposes. Yes - but not for debugging [whatever random piece of code this is in]. Mostly people build only a tiny sub-set of OO.o with debugging enabled to avoid the code bloat & symbol / size explosion that causes. > The Control-C stuff is not Unix only, take a deeper look into > sal/systools/guistdio/guistdio.cpp which I wrote for Windows. > It enables Windows GUI programs to printf to a console ... That sounds *really* cool :-) for sure, I wish I knew about that before; is it documented ? Tor - you might find this useful. > But - my biggest concern is something different. I want those > environment variables to be documented. Cf. the above - this one happens to be pre-documented, and someone has bolded it because it's -so- helpful :-) > There are many many other guys that write issues "give me that env var > for disabling/enabling this feature or that feature". Don't give in to everyone - that would be madness :-) the config engine is clearly the right place for this stuff. However - give in to me ;-) I want to run the same binary in both a debugging 'environment' and also a production one. Thanks for listening anyway - any chance of a re-consider ? ;-) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
