From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: algernon@midgard.debian.net, bug-gnu-emacs@gnu.org,
psg@debian.org, 127943@bugs.debian.org
Subject: Re: Bug#127943: Bug in htmlize.el
Date: Sun, 21 Sep 2003 18:27:54 +0200 [thread overview]
Message-ID: <7704-Sun21Sep2003182753+0300-eliz@elta.co.il> (raw)
In-Reply-To: <9787-Sun21Sep2003163914+0300-eliz@elta.co.il>
> Date: Sun, 21 Sep 2003 16:39:15 +0200
> From: "Eli Zaretskii" <eliz@elta.co.il>
> >
> > I'm curious -- how is "no color" different than "default (unspecified)
> > color"? Is the distinction ever useful? After all, every terminal
> > has some form of color, even when you can't change it! :-)
>
> That's true in theory; but in practice, the Emacs display code cannot
> be easily told that ``no-color'' and ``only 2 colors'' is the same. I
> don't remember the details, sorry: it was a long time ago that I
> hacked the color support for text terminals. But the fact that we
> have a display-color-p predicate is an evidence that these two
> situations are not regarded by Emacs as the same.
Actually, this is slightly inaccurate: these are the reasons why
originally the default colors used the symbol `unspecified'. As
Richard pointed out, `unspecified-fg' and `unspecified-bg' were
invented to handle inverted colors (a.k.a. reverse video) when the
colors are unknown. This happens when you invoke Emacs with the
command "emacs -nw -rv". Neither nil nor `unspecified' can handle
this situation well.
next prev parent reply other threads:[~2003-09-21 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r8njey31.fsf@cachemir.echo-net.net>
[not found] ` <sxsn0y61kix.fsf@florida.arsdigita.de>
[not found] ` <1197.1063152238@mixed>
[not found] ` <m3znhd54dn.fsf@xemacs.org>
[not found] ` <83k784rl0h.wl%algernon@bonehunter.rulez.org>
[not found] ` <m365jnahp7.fsf@hniksic.iskon.hr>
[not found] ` <83ad8zryyx.wl%algernon@midgard.debian.net>
2003-09-20 20:40 ` Bug#127943: Bug in htmlize.el Hrvoje Niksic
2003-09-21 12:36 ` Eli Zaretskii
2003-09-21 12:19 ` Hrvoje Niksic
2003-09-21 14:39 ` Eli Zaretskii
2003-09-21 16:27 ` Eli Zaretskii [this message]
2003-09-21 13:29 ` 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=7704-Sun21Sep2003182753+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=127943@bugs.debian.org \
--cc=algernon@midgard.debian.net \
--cc=bug-gnu-emacs@gnu.org \
--cc=psg@debian.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 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).