user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Dmitry Alexandrov <321942@gmail.com>
To: Mateusz Loskot <mateusz@loskot.net>
Cc: Eric Wong <e@80x24.org>,  meta@public-inbox.org
Subject: Re: Default theme
Date: Sat, 23 Feb 2019 04:19:36 +0300
Message-ID: <87a7in47yv.fsf@gmail.com> (raw)
In-Reply-To: <CABUeae_EPNS=Pq8L_ZUXKf1=aBNPU4nAzVBBJJHtxT6pMka6FA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

Mateusz Loskot <mateusz@loskot.net> wrote:
> On Fri, 22 Feb 2019 at 09:50, Eric Wong <e@80x24.org> wrote:
>> The way I see it is:  whatever color scheme I choose will make
>> some people unhappy.  That's why I make sure it's customizable
>> via user CSS and the CSS class names remain stable.
>
> I agree. Then, why not keep the no theme.

I guess, that was a matter of implementing semantic colour highlighting of diffs and code.  Alas, CSS is not Emacs themes and it doesn’t support calculating colours relatively, so you have to either (user-friendly way) make some reasonable assumptions about basic colours or (foolproof way) enforce them.  On the other hand, items of personal taste, such as undecorated links, I believe, got into the published stylesheet simply by mistake.

>> "prefers-color-scheme" media queries may be used to set
>> to respect user preferences in future browsers.

FWIW, Mozilla implemented it a week ago.

Also, there has always been a standard, yet pretty weird, and hence not widely used, way to choose a stylesheet for a given page among several alternatives: <link rel="stylesheet" title="…" …> + ‘Default-Style’ HTTP header.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 13:36 Mateusz Loskot
2019-02-22  8:50 ` Eric Wong
2019-02-22 20:39   ` Dmitry Alexandrov
2019-02-23  2:47     ` Eric Wong
2019-02-23 10:56       ` [PATCH 0/2] ensure user CSS always overrides BOFH CSS Eric Wong
2019-02-23 10:56         ` [PATCH 1/2] usercontent.pm: set "!important" to override BOFH prefs Eric Wong
2019-02-23 10:56         ` [PATCH 2/2] www: prevent '!important' in BOFH-specified CSS Eric Wong
2019-02-23 19:55       ` Default theme Mateusz Loskot
2019-02-22 20:53   ` Mateusz Loskot
2019-02-23  1:19     ` Dmitry Alexandrov [this message]
2019-02-23  2:50       ` Eric Wong
2019-02-23 10:49         ` Eric Wong

Reply instructions:

You may reply publically 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: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7in47yv.fsf@gmail.com \
    --to=321942@gmail.com \
    --cc=e@80x24.org \
    --cc=mateusz@loskot.net \
    --cc=meta@public-inbox.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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror http://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.org/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox