[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Customize Rogue

From: Richard Stallman
Subject: Re: Customize Rogue
Date: Mon, 10 Mar 2003 20:07:16 -0500

    If I see the message and take the pain to do (custom-setq
    var value), I certainly *expect* for custom to be silent from now on,
    because I'm "going through it", even if not interactively. There's
    *nothing* special in using the interactive, forms-like interface, other
    than the fact that it is easier for some people.

I agree.  Custom is meant to be a useful tool for the user, on top
of ordinary Lisp, not a primitive feature.

    See utf-fragment-on-decoding for an extreme example.  It has a huge and
    complicated :set function, and no way to do the same thing outside

If this is something a Lisp program might want to do, we should provide
an easier way to do it.  It could be done by putting that :set code
into a named function for Lisp programs to call.

I don't think we should have set-activate; it should not be necessary.

We should not recommend anything like custom-setq as the way for Lisp
programs to set a parameter.  Something like custom-setq should only
be used when the aim is specifically to fake out Custom.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]