From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Comments on setopt
Date: Mon, 14 Feb 2022 23:01:00 +0000 [thread overview]
Message-ID: <871r05rr2r.fsf@posteo.net> (raw)
Hi Lars,
I'm glad to see the recent addition of the setopt macro. Having have
experimented with similar macros in the past, I wanted to raise these
points:
- Unless it makes more sense for `customize-set-variable' to take care
of it, should there be some type checking with errors or warnings if
the value doesn't match the type of a user option?
- As `customize-set-variable' is being used directly, the "user" theme
is modified, and a customisation might be mirrored in
`custom-set-variables'. This can lead to the unfortunate situation
where your setopt configuration is overriden by the
`custom-set-variables', depending on when and how you load `custom-file'
and when and how the `custom-set-variables' was generated.
- While I don't mind it really, I can imagine that others might object
to the "long" name, when compared to setq. Would a default alias like
"seto" or "setc" be worth it or not?
--
Philip Kaludercic
next reply other threads:[~2022-02-14 23:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 23:01 Philip Kaludercic [this message]
2022-02-15 3:40 ` Comments on setopt Po Lu
2022-02-16 4:12 ` Richard Stallman
2022-02-16 7:04 ` Rudolf Adamkovič
2022-02-16 9:52 ` Phil Sainty
2022-02-16 13:23 ` Stefan Monnier
2022-02-16 22:34 ` Phil Sainty
2022-02-16 22:42 ` Stefan Monnier
2022-02-16 22:57 ` Philip Kaludercic
2022-02-16 7:13 ` Po Lu
2022-02-19 4:54 ` Richard Stallman
2022-02-19 5:07 ` Po Lu
2022-02-19 8:47 ` Eli Zaretskii
2022-02-19 11:13 ` Lars Ingebrigtsen
2022-02-19 11:52 ` Mathias Dahl
2022-02-19 12:35 ` Dmitry Gutov
2022-02-19 14:41 ` Name for `setopt` (was: Comments on setopt) Stefan Monnier
2022-02-19 18:31 ` Comments on setopt Philip Kaludercic
2022-02-19 23:42 ` [External] : " Drew Adams
2022-02-15 9:32 ` Lars Ingebrigtsen
2022-02-15 13:15 ` Stefan Monnier
2022-02-15 17:20 ` Philip Kaludercic
2022-02-17 11:27 ` Lars Ingebrigtsen
2022-02-15 17:17 ` Philip Kaludercic
2022-02-15 19:22 ` Juri Linkov
2022-02-17 11:28 ` Lars Ingebrigtsen
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=871r05rr2r.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.