From: Stefan Kangas <stefan@marxist.se>
To: 56400@debbugs.gnu.org
Subject: bug#56400: Make setopt warn on type mismatch
Date: Tue, 5 Jul 2022 08:32:29 -0700 [thread overview]
Message-ID: <CADwFkmnTFP_291kpAzSotCZ_JgxXK2ZL_UrOmJcCYLhRcCr8ww@mail.gmail.com> (raw)
Severity: wishlist
Why not make `setopt' warn in case there is a type mismatch?
For example, in:
(setopt tetris-buffer-width "hello")
But the type of `tetris-buffer-width' is natnum.
I think this would save users from shooting themselves in the foot.
If they are sure they want to do that, they can use `setq' or
`customize-set-variable' directly.
next reply other threads:[~2022-07-05 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 15:32 Stefan Kangas [this message]
2022-07-05 16:57 ` bug#56400: Make setopt warn on type mismatch Lars Ingebrigtsen
2022-07-05 17:08 ` Stefan Kangas
2022-07-05 17:32 ` Lars Ingebrigtsen
2022-07-05 17:42 ` Stefan Kangas
2022-07-05 18:07 ` Lars Ingebrigtsen
2022-07-05 18:51 ` Juri Linkov
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=CADwFkmnTFP_291kpAzSotCZ_JgxXK2ZL_UrOmJcCYLhRcCr8ww@mail.gmail.com \
--to=stefan@marxist.se \
--cc=56400@debbugs.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 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).