From: Jordon Biondo <jordonbiondo@gmail.com>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: Revisiting `setq-local`s signature
Date: Mon, 30 Jan 2017 13:37:54 -0500 [thread overview]
Message-ID: <CABB6V6qKOKu3NX+mKg0nHT+=K6Nm95F_DqsRKcnP9NN6RKBt1A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
A while ago I brought up the inconstant signatures of `setq`,
`setq-default` and `setq-local`. In short, I want `setq-local` to have the
same signature as `setq` and `setq-local`. (setq* VAR VAL VAR VAL...)
See thread:
http://lists.gnu.org/archive/html/emacs-devel/2015-03/msg00448.html
I appreciate Stefan's input back then, but I'd like to revisit the issue,
get further input, and see if I can change some minds about the issue.
If you believe the variadic signature of `setq` and `setq-default` is not
ideal, consider that backwards compatibility erases any chance that those
two functions will lose that feature, and consider the benefits of being
consistently wrong over being inconsistently right.
Are maintainers and users still opposed to this change? If not I'd be happy
to update the patch from the previous thread.
Regards
-Jordon
[-- Attachment #2: Type: text/html, Size: 1095 bytes --]
next reply other threads:[~2017-01-30 18:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 18:37 Jordon Biondo [this message]
2017-01-31 3:47 ` Revisiting `setq-local`s signature Tino Calancha
2017-01-31 18:13 ` Philipp Stephani
2017-01-31 18:48 ` Tom Tromey
2017-01-31 18:57 ` Drew Adams
2017-01-31 19:13 ` Jordon Biondo
2017-02-01 5:55 ` Tino Calancha
2017-02-02 3:01 ` John Wiegley
2017-02-02 3:34 ` Eli Zaretskii
2017-02-02 14:28 ` Jordon Biondo
2017-02-02 17:35 ` Eli Zaretskii
2017-02-02 17:43 ` Jordon Biondo
2017-02-02 20:31 ` Eli Zaretskii
2017-02-08 15:59 ` Jordon Biondo
2017-02-10 8:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABB6V6qKOKu3NX+mKg0nHT+=K6Nm95F_DqsRKcnP9NN6RKBt1A@mail.gmail.com' \
--to=jordonbiondo@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.