From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ship Mints <shipmints@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Eli Zaretskii <eliz@gnu.org>,
73098@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#73098: setopt float warning unexpected
Date: Fri, 13 Sep 2024 15:09:12 -0400 [thread overview]
Message-ID: <jwv8qvvfk4n.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAN+1HboWuLnisWh2qzzwQ85TzpmN790me9MrvQjsfd0gxvVi+A@mail.gmail.com> (Ship Mints's message of "Fri, 13 Sep 2024 11:11:18 -0400")
> If you encounter a discrepancy that cannot be addressed by amending
> the type specified by a setopt call, and you can deem the desired
> type compatible nonetheless, use setq. If the user option has an
> associated \"setter\" you may invoke it manually using ???"
You're here trying to describe workarounds to use in case of bugs
(either the value you set is wrong, or the type (or type-checker) is
wrong). We usually don't do that in docstrings.
Stefan
next prev parent reply other threads:[~2024-09-13 19:09 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
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 [this message]
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=jwv8qvvfk4n.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=73098@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=shipmints@gmail.com \
--cc=stefankangas@gmail.com \
/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).