From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: /
Date: Wed, 3 Jan 2018 21:59:47 +0000 (UTC) [thread overview]
Message-ID: <1514956640.c7e61fd606da3951e427c3c4931d2fb96e391738.gokturk@gentoo> (raw)
Message-ID: <20180103215947.yNYLs1hn7XMQ-qjcDQ_U4siXbnkvt-uonrVo0K8jYQY@z> (raw)
commit: c7e61fd606da3951e427c3c4931d2fb96e391738
Author: Andrey Utkin <andrey_utkin <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 8 18:11:26 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Wed Jan 3 05:17:20 2018 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=c7e61fd6
CSS: let tabs in code blocks render as 4 positions
Per devmanual, in ebuild files only tabs must be used for indentation,
and each tab represents four spaces. However, many snippets of ebuild
code in devmanual use spaces for indentation, making these snippets not
immediately usable for pasting. Snippets indented with tabs, while
technically conformant, look the wrong way.
This change makes tabs-indented snippets look right, making it more
attractive for contributors to use tabs for indentation, and paving the
road for potential conversion of spaces-indented snippets to tabs.
Acked-by: Gokturk Yuksek <gokturk <AT> gentoo.org>
devmanual.css | 3 +++
1 file changed, 3 insertions(+)
diff --git a/devmanual.css b/devmanual.css
index 6f24642..1507558 100644
--- a/devmanual.css
+++ b/devmanual.css
@@ -154,6 +154,9 @@ div.figure, div.figure p {
code, pre, tt {
font-family: monospace;
+ tab-size: 4;
+ -o-tab-size: 4;
+ -moz-tab-size: 4;
}
blockquote.epigraph p {
next reply other threads:[~2018-01-03 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 5:57 Göktürk Yüksek [this message]
2018-01-03 21:59 ` [gentoo-commits] proj/devmanual:master commit in: / Göktürk Yüksek
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=1514956640.c7e61fd606da3951e427c3c4931d2fb96e391738.gokturk@gentoo \
--to=gokturk@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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