From: Drew Adams <drew.adams@oracle.com>
To: 60168@debbugs.gnu.org
Subject: bug#60168: 28.2; Doc string of `face-spec-recalc'
Date: Sat, 17 Dec 2022 20:57:48 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883989997621634C46DFEBF3E79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
I don't understand this doc string.
What is the meaning of the indented occurrences of `|'?
How is one supposed to read this? Are there 3 sources? 5 sources? 6
sources?
Is `|' supposed to separate the sources (so there are only 3)? If so,
how to understand the one that starts with `(theme...)' and ends with
`(X resources...)'?
Why are some things - which clearly are NOT code - in parens? Of what
use are the parens here? Why `(defface default spec)' (parens) but
`defface override spec' (no parens)?
And lest someone claim that this is just a "helper" function or
"internal": this is the meat of what `face-spec-set' does. If this
isn't described here then it should be described for `face-spec-set'.
(And in any case, the doc string here needs to be fixed or removed.)
In GNU Emacs 28.2 (build 2, x86_64-w64-mingw32)
of 2022-09-13 built on AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.19044
System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.2251)
Configured using:
'configure --with-modules --without-dbus --with-native-compilation
--without-compress-install CFLAGS=-O2'
Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
XPM ZLIB
(NATIVE_COMP present but libgccjit not available)
next reply other threads:[~2022-12-17 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 20:57 Drew Adams [this message]
2022-12-18 9:01 ` bug#60168: 28.2; Doc string of `face-spec-recalc' 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB54883989997621634C46DFEBF3E79@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=60168@debbugs.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.