unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: Comments on setopt
Date: Tue, 15 Feb 2022 21:22:58 +0200	[thread overview]
Message-ID: <868rucq9a5.fsf@mail.linkov.net> (raw)
In-Reply-To: <871r04qxu4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 15 Feb 2022 10:32:35 +0100")

>> - 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?
>
> `customize-set-variable' should indeed warn/error out if the value is
> invalid.

Maybe like `set-variable' checks for custom-type.



  parent reply	other threads:[~2022-02-15 19:22 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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868rucq9a5.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).