From: "Mattias Engdegård" <mattiase@acm.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
tomas@tuxteam.de, Stephen Leake <stephen_leake@stephe-leake.org>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: master 68ae6fa: Improved light/dark colour predicate (bug#41544)
Date: Thu, 18 Jun 2020 22:04:30 +0200 [thread overview]
Message-ID: <0F5723EE-113E-4D3B-9BD8-D5327B3E87A1@acm.org> (raw)
In-Reply-To: <ab96761f-1d6a-49ce-a216-d749124bda79@default>
18 juni 2020 kl. 21.35 skrev Drew Adams <drew.adams@oracle.com>:
> But if there are different eyes, screens, whatever,
> would it make sense to use a defvar, or even a defcustom,
> instead of a defconst? Why decide this definitively
> at design time? Does it make sense to hard-code it?
Well, it isn't really hard-coded in the sense that it cannot be changed later on, or be turned into a defcustom; both perfectly possible. However, I'd rather not get carried away and add yet another customisable variable before we have more substantial evidence that it would make sense to do so.
next prev parent reply other threads:[~2020-06-18 20:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200610181238.9796.44750@vcs0.savannah.gnu.org>
[not found] ` <20200610181239.947C4204DF@vcs0.savannah.gnu.org>
2020-06-10 19:20 ` master 68ae6fa: Improved light/dark colour predicate (bug#41544) Stefan Monnier
2020-06-10 19:34 ` Mattias Engdegård
2020-06-10 20:01 ` Stefan Monnier
2020-06-11 5:15 ` Yuri Khan
2020-06-11 16:15 ` Mattias Engdegård
2020-06-11 19:22 ` Yuri Khan
2020-06-12 15:50 ` Mattias Engdegård
2020-06-12 16:22 ` tomas
2020-06-12 18:36 ` Yuri Khan
2020-06-13 10:55 ` Mattias Engdegård
2020-06-12 19:02 ` Drew Adams
2020-06-12 19:09 ` Stephen Leake
2020-06-18 19:28 ` Mattias Engdegård
2020-06-18 19:35 ` Drew Adams
2020-06-18 20:04 ` Mattias Engdegård [this message]
2020-06-18 20:32 ` Drew Adams
2020-06-21 7:51 ` Mattias Engdegård
2020-06-18 19:40 ` Basil L. Contovounesios
2020-06-18 19:58 ` Mattias Engdegård
2020-06-13 4:05 ` Richard Stallman
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=0F5723EE-113E-4D3B-9BD8-D5327B3E87A1@acm.org \
--to=mattiase@acm.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.org \
--cc=tomas@tuxteam.de \
--cc=yuri.v.khan@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).