From: Ship Mints <shipmints@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
73098@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#73098: setopt float warning unexpected
Date: Mon, 9 Sep 2024 11:35:39 -0400 [thread overview]
Message-ID: <CAN+1Hbpgu7KfZL+_=K4U7k+1_UNv0_MSzV8fewG7dns5=3yn4g@mail.gmail.com> (raw)
In-Reply-To: <86tteovoc8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Perhaps an alternative macro `setopt-relaxed"? Documentation should suggest
contacting package authors to request improvements (it's a very slow
process to get misspecified packages updated and not all authors mean what
they say when they themselves don't use the customize system--this group
must know this all too well).
On Mon, Sep 9, 2024 at 11:28 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Cc: Eli Zaretskii <eliz@gnu.org>, 73098@debbugs.gnu.org
> > Date: Mon, 09 Sep 2024 17:11:40 +0200
> >
> > Ship Mints <shipmints@gmail.com> writes:
> >
> > > I'm suggesting that there will be noise from people who convert from a
> > > working (setq some-package-option 2) to (setopt some-package-option
> > > 2). This is not a request to change the elisp type system, it is a
> > > request to consider if setopt's / customize internals should be
> > > relaxed to the equivalent of #'= for these simple cases.
> >
> > How about adding an option letting the user disable the type checking of
> > some options?
>
> Like what? Would we accept, for example, a string where the type is
> 'symbol'? Or any value where type is 'boolean'?
>
> And I'm also not sure we want this: presumably, if the defcustom's
> author specified a type, they meant it, no?
>
> Which is why I asked for opinions (but for now got only yours).
>
> Stefan, WDYT?
>
[-- Attachment #2: Type: text/html, Size: 2191 bytes --]
next prev parent reply other threads:[~2024-09-09 15:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 13:14 bug#73098: setopt float warning unexpected Ship Mints
2024-09-08 6:06 ` Eli Zaretskii
2024-09-08 10:59 ` Ship Mints
2024-09-08 11:08 ` Eli Zaretskii
2024-09-08 11:15 ` Ship Mints
2024-09-09 15:11 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-09 15:28 ` Eli Zaretskii
2024-09-09 15:35 ` Ship Mints [this message]
2024-09-09 16:40 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-09 16:38 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-09 17:37 ` Eli Zaretskii
2024-09-09 17:46 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-09 19:02 ` Eli Zaretskii
2024-09-09 22:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 8:22 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 11:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 11:36 ` Eli Zaretskii
2024-09-11 22:53 ` Stefan Kangas
2024-09-13 15:11 ` Ship Mints
2024-09-13 15:28 ` Eli Zaretskii
2024-09-13 17:14 ` Ship Mints
2024-09-13 18:27 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 9:35 ` Eli Zaretskii
2024-09-13 19:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-13 19:26 ` Ship Mints
2024-09-13 19:38 ` Ship Mints
2024-09-14 6:15 ` Eli Zaretskii
2024-09-14 12:33 ` Ship Mints
2024-09-08 11:39 ` Andreas Schwab
2024-09-08 12:28 ` Ship Mints
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='CAN+1Hbpgu7KfZL+_=K4U7k+1_UNv0_MSzV8fewG7dns5=3yn4g@mail.gmail.com' \
--to=shipmints@gmail.com \
--cc=73098@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).