[...] > With the xvnc example, I better understand the kind of situation where > a field value might end up directly in a gexp, though I’m still unsure > whether use of *unspecified* really makes things worse. At least, > because it lacks a read syntax, the problem is caught early on; whereas > with 'unset, you might end up stuffing 'unset in your config file > without noticing. I've been experimenting a lot with define-configuration recently and it gives you little chance to shoot yourself in the foot; it knows maybe values are not to be serialized, and won't wrote such values to config files. Thanks, Maxim