From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: Comments on setopt
Date: Thu, 17 Feb 2022 12:28:11 +0100 [thread overview]
Message-ID: <87r181n35g.fsf@gnus.org> (raw)
In-Reply-To: <868rucq9a5.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 15 Feb 2022 21:22:58 +0200")
Juri Linkov <juri@linkov.net> writes:
>> `customize-set-variable' should indeed warn/error out if the value is
>> invalid.
>
> Maybe like `set-variable' checks for custom-type.
Right. I've now added that for setopt. And since it's not relying on
customize-set-variable any more, that means that we don't have to break
customize-set-variable compatibility. 😀
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-17 11:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 23:01 Comments on setopt Philip Kaludercic
2022-02-15 3:40 ` 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 [this message]
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=87r181n35g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=philipk@posteo.net \
/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.