From: Yuri Khan <yuri.v.khan@gmail.com>
To: goncholden <goncholden@protonmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: checking for light or dark background
Date: Wed, 2 Feb 2022 21:48:51 +0700 [thread overview]
Message-ID: <CAP_d_8WY8UWuNv0sz6X=gD1LP975f8PmO45wwY-u1dPYARCacQ@mail.gmail.com> (raw)
In-Reply-To: <KVkxOi0o6gG0XkpbDu2OA5V2KLpYY04RnrifhlpMfWxp-l-W0yMK_EQiz--CSfSHYq4k7oTzOHxrwKWi_pFG2MEUyx2c5wTy4xTTAYcjbDI=@protonmail.com>
On Wed, 2 Feb 2022 at 21:05, goncholden <goncholden@protonmail.com> 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.
(frame-parameter FRAME 'background-mode), on the other hand, uses only
public, documented symbols, guaranteed to be available and working
well into the next century. (Exaggerating a bit here, but you get the
idea.)
next prev parent reply other threads:[~2022-02-02 14:48 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 [this message]
2022-02-03 4:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
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='CAP_d_8WY8UWuNv0sz6X=gD1LP975f8PmO45wwY-u1dPYARCacQ@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=goncholden@protonmail.com \
--cc=help-gnu-emacs@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.