Re: utf-translate-cjk-mode

[Dave Love]

address@hidden (Kai Großjohann) writes:

>   I don't know whether custom-setq is the right name for this.

`custom-setq' is unlikely to be right for anything.  Many people seem
to be under the mistaken impression that `customize-option' is
equivalent to `setq'.  The default setter is actually `setq-default',
as is clear particularly for local minor modes.

It probably is useful to be able to do the equivalent of
`customize-option' programmatically.

> * Implement a coding standard that requires that there be a Lispish
>   way for all settings that can be done via Customize, and that the
>   Lispish way is documented with the Customize options, and that the
>   Customize way is documented with the Lispish
>   function/variable/whatever.

Custom isn't un-`Lispish'.  On the contrary, it's typically Lisp-ish
to build an embedded language system to abstract tasks.  And since
Custom is written in Lisp, you must be able to write code that does
the same as the Custom user interface.

I don't believe there should be such a prescriptive coding standard.
It sounds as though you're ruling out Custom themes, for a start.

-- 
If you give someone Fortran, he has Fortran.  If you give someone
Lisp, he has any language he pleases.  -- Guy Steele