Of course, that cleanup I did earlier in which I rationalised all
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Mon, 27 Jan 2003 23:18:16 +0000 (23:18 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Mon, 27 Jan 2003 23:18:16 +0000 (23:18 +0000)
commit88103a480c4ed348f28fc9fc20cfc4641206b92c
treef7b3aff2a8535fdeeeb1af30a387a7ab79c56190
parent37ca32ed18b3e104c1056713f5112b90c6547e89
Of course, that cleanup I did earlier in which I rationalised all
the various `yes/no/maybe' enums into one common one missed a vital
point: all those enums mapped on to integers in different ways,
which affected the format of stored settings. Arrgh. So now
settings.c contains yet more painful warts and I'm _really_ starting
to think it's about time we designed a new set of human-usable
config keywords and retired this lot to the status of Unpleasant
Backwards-Compatibility Relic.

git-svn-id: svn://svn.tartarus.org/sgt/putty@2735 cda61777-01e9-0310-a592-d414129be87e
settings.c