Controller can't unset httpsproxy if it doesn't resolve
If you use Vidalia to setconf your httpsproxy, Tor will use that httpsproxy. If you're on a laptop though and you shutdown and start up Tor on a different network, where you don't want to be using that httpsproxy (and where it doesn't resolve), Tor won't start. There's no way for the controller to unset the httpsproxy, because the way the controller approach is designed you start up Tor and then setconf the new config choices.
The result: there's no way to stop using an httpsproxy if you're in an environment that can't resolve the one you configured earlier.
Is this something that can be fixed inside Tor (e.g. by not failing)? Or do we need to change the controller recommendations to be able to edit your torrc for you before starting Tor? Poor options all around.
I'm not sure if this should be in the Tor Client component or the Vidalia component. Picking Tor for now.