Re: Customize Rogue

[Luc Teirlinck]

Juanma Barranquero wrote:

   I know that.

   > (custom-setq inhibit-startup-echo-area-message (user-login-name))
   > 
   > would not get around that problem.

   Wouldn't? The custom-setq I'm talking about would have the *exact*
   semantics of doing M-x customize-variable MY-VAR, setting the value to
   VALUE and then chosing "Save for Future Sessions"... So it would, by
   definition.

If I copy that line literally from your .emacs, then what is going to
prevent that line from having exactly the same effect in my .emacs
than it has in yours?  The VALUE you are going to enter through
customize would be "lektu" or whatever, so that value would really
have no effect in my .emacs, where "teirllm" would be required.

   > I am not necessarily saying that you do not have a point, only that if
   > you do, your example seems badly chosen.  (Unless I am completely
   > misunderstanding it.)

   The first one that crossed my mind. But what about those variables whose
   docstring says "Setting this variable directly will have no effect, you
   have to use customize"...? I want to have the option of setting the
   variable directly and getting the customization effect.

I actually agree with the above.  But what does this have to do with
`inhibit-startup-echo-area-message'?  It definitely is not one of
those variables.

Sincerely,

Luc.