From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
Stefan Kangas <stefan@marxist.se>, Eli Zaretskii <eliz@gnu.org>
Cc: "47574@debbugs.gnu.org" <47574@debbugs.gnu.org>
Subject: bug#47574: [External] : bug#47574: 'match' face is too bright
Date: Thu, 15 Apr 2021 16:04:06 +0000 [thread overview]
Message-ID: <SA2PR10MB44742943E1BFC2045E390C49F34D9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <8a85c907-99da-2051-3e42-cdd58237c41b@yandex.ru>
> > > Wish we had some dark-background users
> > > in this discussion.
> >
> > Why limit a discussion of changing some
> > default behavior to a bug thread?
>
> I'm using a bug report to be able to post a sane
> reference to the discussion in the resulting commit message.
Nothing wrong with referring to a bug #/thread
in a commit msg -- after soliciting discussion,
and discussing, in emacs-devel.
The question was about _limiting_ discussion to
a bug thread. And the answer is?
> Please feel free to post to emacs-devel to notify
> anybody interested that such discussion is taking place here.
I'll let you do that, if you think it's relevant.
Maybe you'd like to do that if and when the
discussion here comes to trying to decide
(1) whether to change the default for this face
and, if so, (2) what to change it to.
I think it makes sense to discuss default changes
in emacs-devel (and not just to notify that list
that there's a discussion here about a possible
default change). Just one opinion.
prev parent reply other threads:[~2021-04-15 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 23:42 bug#47574: 'match' face is too bright Dmitry Gutov
2021-04-03 0:13 ` bug#47574: [External] : " Drew Adams
2021-04-03 6:39 ` Eli Zaretskii
2021-04-03 18:26 ` Dmitry Gutov
2021-04-14 14:55 ` Stefan Kangas
2021-04-15 13:57 ` Dmitry Gutov
2021-04-15 14:38 ` Eli Zaretskii
2021-04-18 10:16 ` Stefan Kangas
2021-04-22 0:13 ` Dmitry Gutov
2021-05-06 11:07 ` Lars Ingebrigtsen
2021-04-15 14:56 ` bug#47574: [External] : " Drew Adams
2021-04-15 15:43 ` Dmitry Gutov
2021-04-15 16:04 ` Drew Adams [this message]
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=SA2PR10MB44742943E1BFC2045E390C49F34D9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=47574@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).