From: Eli Zaretskii <eliz@gnu.org>
To: Ship Mints <shipmints@gmail.com>
Cc: michael_heerdegen@web.de, 73098@debbugs.gnu.org,
monnier@iro.umontreal.ca, stefankangas@gmail.com
Subject: bug#73098: setopt float warning unexpected
Date: Sat, 14 Sep 2024 09:15:18 +0300 [thread overview]
Message-ID: <861q1mkbgp.fsf@gnu.org> (raw)
In-Reply-To: <CAN+1HboQqH0-Zbj3tkXT8KPSF2AmnMD-Opbro8C39J-W+QSGTg@mail.gmail.com> (message from Ship Mints on Fri, 13 Sep 2024 15:38:28 -0400)
> From: Ship Mints <shipmints@gmail.com>
> Date: Fri, 13 Sep 2024 15:38:28 -0400
> Cc: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
> Michael Heerdegen <michael_heerdegen@web.de>, 73098@debbugs.gnu.org
>
> The warning messages can be misleading. e.g., when trying to set tab-bar-format-tabs-groups to include a
> simple lambda, it complains about the wrong thing. It does match the hook type, but does not match the
> hard-coded list of options.
>
> (setopt tab-bar-format
> `(
> tab-bar-format-tabs-groups
> (lambda () " ") ; tab-bar-separator
> ))
>
> ■ Warning (emacs): Value '(nil tab-bar-format-tabs-groups (lambda nil " "))' does not match type hook
I don't get a warning when I evaluate the above. Is this in "emacs -Q"?
next prev parent reply other threads:[~2024-09-14 6:15 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
2024-09-13 19:26 ` Ship Mints
2024-09-13 19:38 ` Ship Mints
2024-09-14 6:15 ` Eli Zaretskii [this message]
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=861q1mkbgp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73098@debbugs.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).