From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ship Mints <shipmints@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "michael_heerdegen@web.de" <michael_heerdegen@web.de>,
"73098@debbugs.gnu.org" <73098@debbugs.gnu.org>,
"stefankangas@gmail.com" <stefankangas@gmail.com>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>
Subject: bug#73098: setopt float warning unexpected
Date: Fri, 13 Sep 2024 18:27:47 +0000 [thread overview]
Message-ID: <DS7PR10MB5232D6467598C9D7F5AD41ACF3652@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAN+1HbrUeQno9Ldzc5C6DFq8Hv+DJmLgjjV9mFH1kmfL2-Hd0Q@mail.gmail.com>
> setopt will execute any custom-set form
^^^^^^^^^^^^^^^
> associated with VARIABLE
1. "custom-set form" isn't mentioned, let alone
defined, in the Elisp manual. Should this
say "any defcustom :set function" instead?
2. What about what I suppose you would call a
"custom-init form", in other words, what the
Elisp manual calls ":initialize function"?
next prev parent reply other threads:[~2024-09-13 18:27 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 [this message]
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=DS7PR10MB5232D6467598C9D7F5AD41ACF3652@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=bug-gnu-emacs@gnu.org \
--cc=73098@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).