all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ship Mints <shipmints@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73098@debbugs.gnu.org
Subject: bug#73098: setopt float warning unexpected
Date: Sun, 8 Sep 2024 06:59:31 -0400	[thread overview]
Message-ID: <CAN+1HbpuDMt5EhPKcZbqKPHfC4BUQsDxo2=quviOE=2Bj=+wOw@mail.gmail.com> (raw)
In-Reply-To: <86r09uwuf3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Yessir. I was talking about users' likely expectations for type coercion.
There are cases in elisp where numeric type coercion is the default,
e.g., (= 2.0 2) is t. I expected it to be so here, too.

If you feel this is moot, then so be it.

On Sun, Sep 8, 2024 at 2:07 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Ship Mints <shipmints@gmail.com>
> > Date: Sat, 7 Sep 2024 09:14:54 -0400
> >
> > This one bit me yesterday on Emacs 29.3 as I was revising my init file
> (for the thousandth time this week).
> >
> > As setopt becomes more widely recommended, people will likely encounter
> situations like the below where they
> > expect constant numeric types to be coerced.
> >
> > (defcustom temp-float "Float"
> >   "Float type."
> >   :type 'float)
> >
> > (setopt temp-float 2.0) ; works
> > (setopt temp-float 2) ; Warning (emacs): Value '2' does not match type
> float
>
> If you are going to allow integer values, shouldn't :type be 'number,
> not 'float?  The documentation of 'float says:
>
>   ‘float’
>        The value must be floating point.
>
> "Must be floating point."  The value 2 isn't.
>

[-- Attachment #2: Type: text/html, Size: 1832 bytes --]

  reply	other threads:[~2024-09-08 10:59 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 [this message]
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
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

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

  git send-email \
    --in-reply-to='CAN+1HbpuDMt5EhPKcZbqKPHfC4BUQsDxo2=quviOE=2Bj=+wOw@mail.gmail.com' \
    --to=shipmints@gmail.com \
    --cc=73098@debbugs.gnu.org \
    --cc=eliz@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 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.