Re: Further problem with recent changes to custom-magic-alist.

[Luc Teirlinck]

We are talking about:

You have set this %c and saved it through Customize in your init file.

Richard Stallman wrote:

   So I think the best way to shorten this is to delete "through Customize".

That would be very misleading.  There are two ways a user can set an
option permanently:  through Custom and by writing code in his init
file.  Once "through Customize" is deleted, the message seems to say
that the user did the latter:

You have set this %c and saved it in your init file.

   Telling the user the value has been saved in the init file may help
   users understand what is going on.

But the State message is not the place to try to explain how Custom is
implemented.  The user is already reminded that things are written in
his init file each time he saves an option.

Sincerely,

Luc.