all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mirek Kaim <mirek.kaim@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "nljlistbox2@gmail.com" <nljlistbox2@gmail.com>,
	"larsi@gnus.org" <larsi@gnus.org>, "rms@gnu.org" <rms@gnu.org>,
	"cloos@jhcloos.com" <cloos@jhcloos.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Turning off colorization
Date: Mon, 10 Nov 2014 19:37:48 +0100	[thread overview]
Message-ID: <COL131-W8523827475F2558361A7584800@phx.gbl> (raw)
In-Reply-To: <831tpbni05.fsf@gnu.org>

> From: eliz@gnu.org
>
> Please take a look at lisp/term/xterm.el: modern terminal emulators
> report their background color as rgb:NUM1/NUM2/NUM3 rgb triplets.
> This allows Emacs to interpret the color itself, not its name.
>

my mistake. i recall seeing a method to check if the background is being reported pasted here by someone, and it didn't return rgb triplet, just the color name afair.

still, i think using the full 256-color palette for things like html rendering under the terminal should be the way to go - and by that i mean that either things are being displayed using a user-defined terminal/emacs theme combo (discarding the colors defined by a website), or colors are properly handled - and then the background, if not defined, should be a default specific for a web browser, not the default background in emacs, because then it's bound to be wrong.

either it'll behave like a proper web browser, handling everything and having own default colors, or it'll have to discard all colors alltogether to guarantee readable results in every case. there's no perfect 'inbetween' solution, imho. one can't just mix up colors defined by some terminal and/or emacs theme with colors defined by a website, because then what - 'oh, this combination will be unreadable, lets change this color a bit so that the user won't complain'? i saw something along that line here not so long ago - ensuring that the page will stay readable. why bother? all that's needed is proper color handling, as good as possible on target display (wether it's rgb gui or 256-color terminal, doesn't matter).

it is website's author responsibility to make it readable. all that's needed is proper display of all the colors defined. in that regard, turning off colorization for terminals unable to report their background color is kinda pointless. all that matters is if 256 colors are supported - because if not, then there's no sure way to display a website in readable manner without discarding all rainbowy stuff. on the other side, if 256 colors are supported, then the current background shouldn't matter and in case of a website display, shouldn't be used at all.


unic0rn

 		 	   		  


  reply	other threads:[~2014-11-10 18:37 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 16:43 Turning off colorization Richard Stallman
2014-11-04 17:11 ` Phillip Lord
2014-11-05  4:57   ` Richard Stallman
2014-11-05  9:11     ` David Kastrup
2014-11-05 11:31       ` Ted Zlatanov
2014-11-05 11:51         ` Tassilo Horn
2014-11-05 12:49           ` Andreas Schwab
2014-11-05 13:05             ` Tassilo Horn
2014-11-05 11:52         ` Phillip Lord
2014-11-05 12:03           ` Ted Zlatanov
2014-11-05 12:30             ` Phillip Lord
2014-11-05 12:23         ` Lars Magne Ingebrigtsen
2014-11-05 12:52           ` Andreas Schwab
2014-11-05 17:06             ` Lars Magne Ingebrigtsen
2014-11-05 17:30               ` Eli Zaretskii
2014-11-05 17:35               ` Andreas Schwab
2014-11-05 19:56                 ` Lars Magne Ingebrigtsen
2014-11-05 20:17                   ` Eli Zaretskii
2014-11-05 12:55           ` Tassilo Horn
2014-11-05 13:00           ` Yoni Rabkin
2014-11-05 14:00           ` James Cloos
2014-11-05 18:13             ` Richard Stallman
2014-11-05 23:37               ` James Cloos
2014-11-06 10:05                 ` David Kastrup
2014-11-06 15:26                   ` Stefan Monnier
2014-11-06 16:03                     ` Alan Mackenzie
2014-11-06 16:53                       ` Stefan Monnier
2014-11-07  7:13                         ` Richard Stallman
2014-11-07 14:43                           ` Stefan Monnier
2014-11-08  6:44                             ` Richard Stallman
2014-11-08 15:26                               ` Stefan Monnier
2014-11-09 20:06                                 ` Richard Stallman
2014-11-07  7:12                     ` Richard Stallman
2014-11-05 15:02         ` Stefan Monnier
2014-11-06 20:13           ` N. Jackson
2014-11-06 21:42             ` Tim Cross
2014-11-06 23:14             ` Stefan Monnier
2014-11-07  0:10               ` Daniel Colascione
2014-11-07  4:13                 ` Stefan Monnier
2014-11-05 18:12       ` Richard Stallman
2014-11-05 11:05     ` Phillip Lord
2014-11-04 20:59 ` Nic Ferrier
     [not found]   ` <CAG-q9=a+nTM3KhYeBfzvSZOWKMjdDgaUyQw25_NkAkoad3QwOw@mail.gmail.com>
2014-11-05  1:09     ` Kelvin White
2014-11-05  2:10       ` Stephen J. Turnbull
2014-11-05  8:23         ` Harald Hanche-Olsen
2014-11-06 16:47 ` N. Jackson
2014-11-06 17:36   ` Eli Zaretskii
2014-11-06 19:55     ` N. Jackson
2014-11-06 18:00   ` Wolfgang Jenkner
2014-11-06 19:44     ` N. Jackson
2014-11-06 19:44   ` Tassilo Horn
2014-11-06 19:49     ` Eli Zaretskii
2014-11-07  6:36       ` Tassilo Horn
2014-11-07  7:06         ` Eli Zaretskii
2014-11-07  7:59           ` Tassilo Horn
2014-11-07  9:00             ` Eli Zaretskii
2014-11-06 21:55   ` Lars Magne Ingebrigtsen
2014-11-07  0:04   ` James Cloos
2014-11-07 13:57     ` Gregor Zattler
2014-11-07 14:02       ` Eli Zaretskii
2014-11-07 14:47         ` Gregor Zattler
2014-11-07 15:06           ` Eli Zaretskii
2014-11-07 15:27             ` Gregor Zattler
2014-11-07 16:59       ` James Cloos
2014-11-07 19:12         ` Mirek Kaim
2014-11-07 18:36       ` Andreas Schwab
2014-11-07  7:13   ` Richard Stallman
2014-11-07  8:43     ` Eli Zaretskii
2014-11-08  6:44       ` Richard Stallman
2014-11-08  8:15         ` Eli Zaretskii
2014-11-08 21:36           ` Richard Stallman
2014-11-08 22:18           ` James Cloos
2014-11-08 22:30             ` Lars Magne Ingebrigtsen
2014-11-08 22:51               ` James Cloos
2014-11-09  1:30                 ` Lars Magne Ingebrigtsen
2014-11-09  3:51                   ` Eli Zaretskii
2014-11-10 15:29                   ` Mirek Kaim
2014-11-10 16:21                     ` Eli Zaretskii
2014-11-10 18:37                       ` Mirek Kaim [this message]
2014-11-11  1:32                         ` Yuri Khan
2014-11-11 17:58                           ` Mirek Kaim
2014-11-09  3:45                 ` Eli Zaretskii
2014-11-09 14:57                   ` James Cloos
2014-11-09 16:26                     ` Eli Zaretskii
2014-11-09 20:07                   ` Richard Stallman
2014-11-09 20:13                     ` Eli Zaretskii
2014-11-10 19:07                       ` Richard Stallman
2014-11-10 19:57                         ` Eli Zaretskii
     [not found]     ` <<83r3xfs8mx.fsf@gnu.org>
2014-11-07 14:43       ` Drew Adams
2014-11-07 15:28         ` Stefan Monnier
2014-11-07 15:40           ` Eli Zaretskii
2014-11-07 16:08             ` Stefan Monnier
2014-11-08  6:44             ` Richard Stallman
2014-11-09  4:14 ` Paul W. Rankin
2014-11-09 20:08   ` Richard Stallman
2014-11-09 22:03   ` Stefan Monnier
2014-11-10  1:41     ` Paul Rankin

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=COL131-W8523827475F2558361A7584800@phx.gbl \
    --to=mirek.kaim@outlook.com \
    --cc=cloos@jhcloos.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=nljlistbox2@gmail.com \
    --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.