From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, David Gow <davidgow@google.com>,
Sadiya Kazi <sadiyakazi@google.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH RFC] docs: Add more information to the HTML sidebar
Date: Mon, 23 Jan 2023 09:05:05 +0900 [thread overview]
Message-ID: <6b2e496f-d7f6-abea-6bbd-4b12fea76a68@gmail.com> (raw)
In-Reply-To: <fa426691-c76a-8ab0-4975-6edacc9cb247@gmail.com>
Hi Jon,
On Fri, 20 Jan 2023 23:09:34 +0900, Akira Yokosawa wrote:
...
>
> I have mostly the same list of possible improvements.
>
> As for the "where am I?" syndrome, it would be helpful if the sidebar
> could be scrolled independently.
>
> I'd really like to suggest some code changes, but unable to do so.
There is a related question at stackoverflow [1].
The CSS tweak mentioned in its answer works like a charm.
Can you try the changes below on top of this RFC patch?
[1]: https://stackoverflow.com/questions/57031848/sphinx-alabaster-theme-scroll-inside-of-fixed-sidebar
Thanks, Akira
-------------------------------
diff --git a/Documentation/conf.py b/Documentation/conf.py
index 233f2f585143..6c8ccf3095ac 100644
--- a/Documentation/conf.py
+++ b/Documentation/conf.py
@@ -328,6 +328,7 @@ if html_theme == 'alabaster':
'description': get_cline_version(),
'page_width': '65em',
'sidebar_width': '15em',
+ 'fixed_sidebar': 'true',
'font_size': 'inherit',
'font_family': 'serif',
}
diff --git a/Documentation/sphinx-static/custom.css b/Documentation/sphinx-static/custom.css
index 1ad0899bc8f1..3ec27edeb394 100644
--- a/Documentation/sphinx-static/custom.css
+++ b/Documentation/sphinx-static/custom.css
@@ -11,7 +11,7 @@ div.body h3 { font-size: 130%; }
/* Tighten up the layout slightly */
div.body { padding: 0 15px 0 10px; }
div.sphinxsidebarwrapper { padding: 1em 0.4em; }
-div.sphinxsidebar { font-size: inherit; }
+div.sphinxsidebar { font-size: inherit; max-height: 100%; overflow-y: auto; }
/* Tweak document margins and don't force width */
div.document {
margin: 20px 10px 0 10px;
prev parent reply other threads:[~2023-01-23 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 0:11 [PATCH RFC] docs: Add more information to the HTML sidebar Jonathan Corbet
2023-01-20 2:54 ` Bagas Sanjaya
2023-01-20 13:38 ` Sadiya Kazi
2023-01-20 14:09 ` Akira Yokosawa
2023-01-20 15:19 ` Jonathan Corbet
2023-02-03 2:37 ` Akira Yokosawa
2023-02-03 4:29 ` Sadiya Kazi
2023-01-23 0:05 ` Akira Yokosawa [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=6b2e496f-d7f6-abea-6bbd-4b12fea76a68@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=sadiyakazi@google.com \
/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).