From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 45264@debbugs.gnu.org
Subject: bug#45264: 26.3; `face-remap-set-base' seems to be bugged
Date: Sat, 19 Dec 2020 21:40:06 +0200 [thread overview]
Message-ID: <835z4xtwix.fsf@gnu.org> (raw)
In-Reply-To: <8397c6ee-966d-4d34-9a64-2dde3515cedd@default> (message from Drew Adams on Sat, 19 Dec 2020 11:28:31 -0800 (PST))
> Date: Sat, 19 Dec 2020 11:28:31 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 45264-done@debbugs.gnu.org
>
> > > The confusion is from the doc not saying explicitly
> > > that each element of SPECS is a face spec, and NOT a
> > > face.
> >
> > SPECS has no "elements". SPECS stands for arguments to the function
> > beyond the 1st arg FACE.
>
> As with any &rest, you supply zero or more actual
> args that correspond to SPECS. The function itself
> receives a single list argument that corresponds to
> SPECS.
>
> In the function body, variable SPECS is a list.
> And as the doc says, "Each list element...".
The doc string shouldn't explain how the function's body sees SPECS,
it should explain how to provide those args.
> Please check for the behavior bug I pointed to:
If it doesn't work according to the doc string, then yes, it's a bug.
next prev parent reply other threads:[~2020-12-19 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<dbc9cd7f-c4da-4137-a972-aada49e0f1f1@default>
[not found] ` <<<833602umgb.fsf@gnu.org>
[not found] ` <<4efb5c63-6636-449f-8e2b-4b8533a9cc8c@default>
[not found] ` <<83a6u9tyh1.fsf@gnu.org>
2020-12-19 19:28 ` bug#45264: 26.3; `face-remap-set-base' seems to be bugged Drew Adams
2020-12-19 19:40 ` Eli Zaretskii [this message]
[not found] <<dbc9cd7f-c4da-4137-a972-aada49e0f1f1@default>
[not found] ` <<833602umgb.fsf@gnu.org>
2020-12-19 18:32 ` Drew Adams
2020-12-19 18:58 ` Eli Zaretskii
2020-12-16 0:31 Drew Adams
2020-12-19 10:20 ` Eli Zaretskii
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=835z4xtwix.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45264@debbugs.gnu.org \
--cc=drew.adams@oracle.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).