From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19791@debbugs.gnu.org, rms@gnu.org
Subject: bug#19791: 25.0.50; Bad HTML rendering
Date: Sat, 07 Feb 2015 13:57:04 +0200 [thread overview]
Message-ID: <83r3u2aq9b.fsf@gnu.org> (raw)
In-Reply-To: <87pp9mece5.fsf@building.gnus.org>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 19791@debbugs.gnu.org, rms@gnu.org
> Date: Sat, 07 Feb 2015 12:30:42 +1100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Where's that in the sources?
>
> `shr-color-check' and `shr-color-visible'.
I think I see the problem: it is somehow related to bug #19802. In
particular, even if I do this:
M-: (set-frame-parameter (selected-frame) 'background-color "black") RET
I still get nil from (frame-parameter nil 'background-color). And
shr-color-check relies on the latter to report the background color of
the frame.
So I guess solving that bug will also solve this, or at least move
closer to its solution.
Richard, can you confirm that you see on your system the same problem
with 'background-color' frame parameter on a TTY as described above,
i.e. that setting that parameter in frame's parameter alist doesn't
cause frame-parameter to return the value?
next prev parent reply other threads:[~2015-02-07 11:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 12:41 bug#19791: 25.0.50; Bad HTML rendering Richard Stallman
2015-02-06 13:19 ` Lars Ingebrigtsen
2015-02-06 14:49 ` Eli Zaretskii
2015-02-06 17:14 ` Lars Ingebrigtsen
2015-02-06 18:59 ` Eli Zaretskii
2015-02-07 1:30 ` Lars Ingebrigtsen
2015-02-07 11:57 ` Eli Zaretskii [this message]
2015-02-08 17:52 ` Eli Zaretskii
2015-12-25 22:30 ` Lars Ingebrigtsen
2015-12-26 6:14 ` Richard Stallman
2015-02-07 12:43 ` Richard Stallman
2015-02-07 13:09 ` Eli Zaretskii
2015-02-06 15:31 ` Stefan Monnier
2015-02-06 15:44 ` Eli Zaretskii
2015-02-06 18:09 ` Stefan Monnier
2015-02-07 1:32 ` Lars Ingebrigtsen
2015-02-07 7:14 ` Ivan Shmakov
2015-02-07 7:25 ` Matthew Carter
2015-02-07 11:50 ` Ivan Shmakov
2015-02-07 12:44 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r3u2aq9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19791@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.