Juergen Fenn <[email protected]> writes:
My guess would be that most users will not make this test for
the many setq commands in their init file, but wait for what
package maintainers will recommend as a sample configuration. If
setq remains to work for the time being, I understand that using
setopt is not about whether your configuration is working
properly, but it is rather a recommendation you are free to
comply with or not. Your mileage may vary.
This is not a correct summary of the situation. For over two
years, the recommendations have consistently been to use `setopt'
to set user options in the user's configuration. `setq' is
intended for setting variables in Emacs-Lisp code. There is no
reason to use `setq' for user options. While it might "work" in
some cases, there is no guarantee that it will still be equivalent
for that option in the next Emacs version due to potentially newly introduced
custom setters. Note that `setopt' had been added especially for the purpose
to save
users the effort of individually checking each variable to determine
whether `setq' is sufficient, or if a specific treatment is required.
The difference in required runtime is probably completely negligible.
Michael.
