From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 11430@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#11430: 24.0.96; Customizing `inverse-video' has no effect on session
Date: Mon, 21 Sep 2020 08:33:34 -0700 (PDT) [thread overview]
Message-ID: <c3a72323-2be4-4200-a8b6-6bb23c41c8dc@default> (raw)
In-Reply-To: <875z87mat3.fsf@gnus.org>
> The variable hasn't worked for 20 years (apparently), and this is the
> only bug report about it, which is perhaps a hint that we should just
> remove it.
It doesn't follow that we should remove it.
A bug is a bug. Better to keep this bug open.
Someday, perhaps, Someone(TM) will be motivated
and find a way to fix it. And if not, so what?
What harm does it do to keep a report open for
a recognized bug? When it comes to free software
and its volunteers, no one's career is boosted by
just reducing a bug count as an end in itself.
Or am I missing something?
next prev parent reply other threads:[~2020-09-21 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 16:38 bug#11430: 24.0.96; Customizing `inverse-video' has no effect on session Drew Adams
2012-09-16 23:57 ` Drew Adams
2014-02-09 4:27 ` Lars Ingebrigtsen
2019-11-01 18:16 ` Stefan Kangas
2019-11-01 18:24 ` Drew Adams
2019-11-01 19:58 ` Stefan Kangas
2019-11-01 21:06 ` Drew Adams
2019-11-02 9:45 ` Eli Zaretskii
2019-11-02 11:06 ` Stefan Kangas
2020-09-21 15:03 ` Lars Ingebrigtsen
2020-09-21 15:33 ` Drew Adams [this message]
2020-09-21 15:36 ` Eli Zaretskii
2020-09-22 14:10 ` Lars Ingebrigtsen
2024-06-23 18:52 ` Stefan Kangas
2024-06-23 19:27 ` 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
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=c3a72323-2be4-4200-a8b6-6bb23c41c8dc@default \
--to=drew.adams@oracle.com \
--cc=11430@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).