On Fri, May 30, 2003 at 09:38:19AM +0200, fvwm-workers wrote: > On Thu, May 29, 2003 at 10:23:48PM +0000, Mikhael Goikhman wrote: > > I would like to get some feedback before I try to resolve these bugs. > > These are in both 2.4.x and 2.5.x. > > > > 1) 'UnsetEnv VARNAME' does not work, the variable is not unset, instead > > it gets an empty value "". The fix is obvious, putenv should be called > > with "VARNAME" not "VARNAME=". > > Should be easy to fix without side effects.
Or maybe not. The behaviour of calling putenv() with just a variable name is not defined according to the man page on my Debian system. The unsetenv() function is designed for that purpose, but it does not exist on all systems. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
