A while ago I =
brought up the inconstant signatures of `setq`, `setq-default` and `setq-lo=
cal`. In short, I want `setq-local` to have the same signature as `setq` an=
d `setq-local`. (setq* VAR VAL VAR VAL...)
I appreciate Stefan's input bac=
k then, but I'd like to revisit the issue, get further input, and see i=
f I can change some minds about the issue.
If you believe the var=
iadic signature of `setq` and `setq-default` is not ideal, consider that ba=
ckwards compatibility erases any chance that those two functions will lose =
that feature, and consider the benefits of being consistently wrong over be=
ing inconsistently right.
Are maintainers and users still opposed=
to this change? If not I'd be happy to update the patch from the previ=
ous thread.
As a user, I'm =
still opposed to this change. I don't think consistency is important en=
ough in this case to justify the "worse" signature. Consistency i=
s not a goal in itself, but should serve the goal to increase readability a=
nd lower the barriers for new contributors. I don't think that the simp=
ler signature of setq-local is in any way confusing because of this inconsi=
stency.