From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: checking for light or dark background
Date: Thu, 03 Feb 2022 05:19:53 +0100 [thread overview]
Message-ID: <87y22sponq.fsf@zoho.eu> (raw)
In-Reply-To: CAP_d_8WY8UWuNv0sz6X=gD1LP975f8PmO45wwY-u1dPYARCacQ@mail.gmail.com
Yuri Khan wrote:
>> The problem I was having was that for Emacs 27.2, the
>> command (frame--current-backround-mode nil) was not
>> available. What is the recommendation for Emacs>=28.
>
> You should not rely on (frame--current-background-mode) even
> if it is available. The double dash in its name tells you it
> is a semi-private implementation detail, subject to change
> at any time. You can access it, but when it changes and your
> code breaks, you will get no support.
The designation sure is "semi-private" since it is actually as
public as any other `defun' available on the global
no-namespace market ...
As for what can change and what cannot, I think it is better
to just change what is bad, into something good (or at least
better), and focus on that rather than the supposed status of
the symbol, as communicated by the presence or absence of
a double dash ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-02-03 4:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 9:26 checking for light or dark background goncholden via Users list for the GNU Emacs text editor
2022-02-02 12:56 ` Eli Zaretskii
2022-02-02 13:25 ` goncholden
2022-02-02 13:27 ` goncholden
2022-02-02 14:41 ` Eli Zaretskii
2022-02-02 16:18 ` goncholden
2022-02-02 14:48 ` Yuri Khan
2022-02-03 4:19 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2022-02-03 4:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-08 1:33 ` James Cloos
2022-02-08 3:29 ` Eli Zaretskii
2022-02-20 19:30 ` James Cloos
2022-02-20 20:05 ` Eli Zaretskii
2022-02-21 11:16 ` Yuri Khan
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=87y22sponq.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.