Skip to content

Commit 0499ebd

Browse files
committed
README: FIX code block syntax highlighting.
1 parent 52615fd commit 0499ebd

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

README.rst

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,9 @@ You'll need to fork the `python-docs-fr
5858
button. This creates a copy of the whole project on your github
5959
account: a place where you have the rights to do modifications.
6060

61-
Step by steps::
61+
Step by steps:
62+
63+
.. code-block:: bash
6264
6365
# Git clone your github fork using ssh (replace JulienPalard):
6466
$ git clone git@github.com:JulienPalard/python-docs-fr.git
@@ -70,7 +72,9 @@ Step by steps::
7072
$ git remote add upstream https://github.com/python/python-docs-fr.git
7173
7274
73-
Now you're ready to start a work session, each time you'll start a new task, start here::
75+
Now you're ready to start a work session, each time you'll start a new task, start here:
76+
77+
.. code-block:: shell-session
7478
7579
# To work, we'll need a branch, based on an up-to-date (freshly fetched)
7680
# upstream/3.7 branch, let's say we'll work on glossary so we name
@@ -227,12 +231,16 @@ Simplify git diffs
227231

228232
Git diffs are often crowded with useless line number changes, like:
229233

234+
.. code-block:: diff
235+
230236
-#: ../Doc/library/signal.rst:406
231237
+#: ../Doc/library/signal.rst:408
232238
233239
To tell git they are not usefull information, you can do the following
234240
after ensuring ``~/.local/bin/`` is in your ``PATH``.
235241

242+
.. code-block:: bash
243+
236244
cat <<EOF > ~/.local/bin/podiff
237245
#!/bin/sh
238246
grep -v '^#:' "\$1"
@@ -254,7 +262,9 @@ like::
254262
├── python-docs-fr/
255263
└── cpython/
256264
257-
To clone CPython you may use::
265+
To clone CPython you may use:
266+
267+
.. code-block:: bash
258268
259269
git clone --depth 1 --no-single-branch https://github.com/python/cpython.git
260270

0 commit comments

Comments
 (0)