Re: Incorrect terminology in Customize doc

[Stefan Monnier]

> 1. "user option" has already been defined as something else, so far -
> something related, so potentially confusing.

My understanding is that the original definition of "user option" was: an
option that an end-user (not familiar with Elisp) can change.

This happened to be limited to user-variable-p at the time for lack of
anything else but now also includes faces.

I don't think it's particularly confusing.

> Some of the Customize code already refers to faces + user options together
> as "user options" or "options", BTW.

Indeed, it's a natural extension.

> That will also require, BTW, a term for `user-variable-p'

Why?  It's not like we often need to talk about those particular variables
which are user-variable-p but are not defcustom'd, is it?

And IIRC the last discussion (where we decided that M-x set-variable should
be extended with the functionality of M-x customize-set-variable), we'd like
ultimately to get rid of the distinction between user-variable-p and
custom-izable variables.


        Stefan