From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 0/1] Docs: use RTD dark mode if available
Date: Wed, 1 Dec 2021 09:41:22 +0100 [thread overview]
Message-ID: <20211201094122.1c6fd83d@coco.lan> (raw)
In-Reply-To: <cover.1638346585.git.mchehab+huawei@kernel.org>
Em Wed, 1 Dec 2021 09:22:02 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> Hi Jon,
>
> As we're analyzing some theme alternatives, one of the things that annoys
> me more at our theme is that it doesn't come with a dark mode.
>
> At least here, I strongly prefer dark themes, as it seems to be a lot more
> comfortable to my eyes, specially in the morning.
>
> There's an extension to the RTD theme that allows building the docs with a
> dark theme, with a button to select normal mode.
>
> As this comes almost for free, optionally enable the dark mode extension if
> such theme is installed at the machine.
Too good to be true... It won't work properly, as:
1. Some of the css custom configs at sphinx-static define colors;
2. It sounds that this overlay to RTD theme is missing some classes,
as, at least here, function prototypes from driver-api/media/v4l2-async.html
are written with a black color over a dark gray background.
I'll do more tests. If I find a solution, I'll submit another version.
Thanks,
Mauro
prev parent reply other threads:[~2021-12-01 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 8:22 [PATCH 0/1] Docs: use RTD dark mode if available Mauro Carvalho Chehab
2021-12-01 8:22 ` [PATCH 1/1] docs: add support for dark mode Mauro Carvalho Chehab
2021-12-01 8:41 ` Mauro Carvalho Chehab [this message]
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=20211201094122.1c6fd83d@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.
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 NNTP newsgroup(s).