unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, rms@gnu.org, 19752@debbugs.gnu.org
Subject: bug#19752: 25.0.50; fonts in HTML
Date: Sat, 02 Nov 2019 09:45:08 +0200	[thread overview]
Message-ID: <83mudek9h7.fsf@gnu.org> (raw)
In-Reply-To: <87mudfupwj.fsf@marxist.se> (message from Stefan Kangas on Sat, 02 Nov 2019 00:40:12 +0100)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 02 Nov 2019 00:40:12 +0100
> Cc: Richard Stallman <rms@gnu.org>, 19752@debbugs.gnu.org
> 
> > What does (display-color-cells) return for you?
> 
> FWIW, I tried this on the Linux console and got 8.  I guess ideally
> Richard would try if evaluating the following and see if it solves the
> problem for him:
> 
>     (setq shr-use-colors nil)

This is an option, so "M-x set-variable RET works for it.  No need to
use setq.

More importantly, I think indeed this is on balance the best solution
for these cases.  Emacs automatically maps any color to the closest
available one, but HTML email messages can use color specifications
that will cause both foreground and background convert to the same
colors, which will make the text illegible.

Or maybe shr.el can be taught to use the distant-foreground feature to
handle such cases?

> > -(defcustom shr-use-colors t
> > +(defcustom shr-use-colors (> (display-color-cells) 256)

This is too drastic, IMO.  Most HTML formatted emails use very few
colors and look OK on display even with 8 colors.





  reply	other threads:[~2019-11-02  7:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  1:10 bug#19752: 25.0.50; fonts in HTML Richard Stallman
2015-02-05 17:26 ` Eli Zaretskii
2015-02-06 12:41   ` Richard Stallman
2015-12-25 22:43 ` Lars Ingebrigtsen
2015-12-26  6:14   ` Richard Stallman
2015-12-26 13:46     ` Lars Ingebrigtsen
2015-12-27  2:52       ` Richard Stallman
2019-09-29  8:56 ` Lars Ingebrigtsen
2019-11-01 23:40   ` Stefan Kangas
2019-11-02  7:45     ` Eli Zaretskii [this message]
2020-08-12 16:32       ` Stefan Kangas

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=83mudek9h7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19752@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rms@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).