Re: utf-translate-cjk-mode

[Kai Großjohann]

Dave Love <address@hidden> writes:

> 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.

Sure.  In the case of utf-translate-cjk I did it by copying and
pasting the :set expression into my ~/.emacs file :-)

> 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.

Really?  I just wanted to tell people: if you make it convenient to
set some "option" (in a very generic sense of that word) via Custom,
then also make it convenient to set that option without Custom.  For
example, the copy-paste of the :set expression to enable cjk
translation that I did previously was not convenient, but writing
(utf-translate-cjk-mode 1) into ~/.emacs is convenient.

I don't see how convenience for non-Custom-users can be an obstacle
to Custom themes.
-- 
A preposition is not a good thing to end a sentence with.