Re: Customize Rogue

[David Masterson]

>>>>> Luc Teirlinck writes:

> Custom writes into the "official" custom-file to save the option.
> Is it not the job of the automated tool to now redirect this to the
> file it wants it redirected to and make things function properly?
> Is any other behavior not just a bug in the automated tool?  In
> other words I now again believe that custom-setq would make
> set-activate unnecessary.

Yes, but how would the automated tool do this?  Once the
custom-set-variables list is broken up into custom-setq's (or
set-activates?), they could be put anywhere.  I suppose Custom could
activate the "automated tool" on an exit-hook to allow the tool to
update all of the custom files where things are now stored, but then
how does Custom find these things later to determine the current (set
of) customizations?

-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA