|
From: <no...@so...> - 2002-10-11 17:37:10
|
Bugs item #612672, was opened at 2002-09-21 16:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=465044&aid=612672&group_id=51915 Category: env-switcher functionality Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Jeff Squyres (jsquyres) Assigned to: Jeff Squyres (jsquyres) >Summary: Sentinel "none" val. not totally honored Initial Comment: The following usage scenario shows where the sentinel value "none" doesn't seem to work properly. Setting a value to "none" (at least for the "default" attribute) should actually delete the attribute. $ switcher foo --list default=system_bar exists=true $ switcher foo = user_bar $ switcher foo --list default=user_bar exists=true $ switcher foo = none $ switcher foo --list default=none exists=true Hence, the system value "system_bar" is effectively hidden. One can do a "--rm-attr" on default and get the expected behavior, but since "none" is documented to be a special sentinel value, it should just go ahead and remove the attribute, not just mark it as "none". ---------------------------------------------------------------------- >Comment By: Jeff Squyres (jsquyres) Date: 2002-10-11 10:37 Message: Logged In: YES user_id=11722 This is incorrect, and a classic case of the author forgetting the original intention of a feature. :-) The sentinel "none" is meant to indicate that nothing should occur for that tag. Hence "switcher foo = none" means that the user does not want anything loaded for the foo tag, regardless of what the system-level default is. RTFM (man page) provides ample detail describing that this is the intent of the "none" value. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=465044&aid=612672&group_id=51915 |