Skip to content

Commit 08d6158

Browse files
committed
doc: use ini file syntax highlighting where needed
Signed-off-by: Stewart Smith <[email protected]>
1 parent b27a57a commit 08d6158

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

Diff for: doc/user-guide.rst

+9-3
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ you may keep a configuration file per-machine you test against, to save on
1414
typing out all the IP addresses and login credentials.
1515

1616
For example, this ``witherspoon.conf`` file will connect to a Witherspoon
17-
machine: ::
17+
machine:
18+
19+
.. code-block:: ini
1820
1921
[op-test]
2022
bmc_type=OpenBMC
@@ -33,7 +35,9 @@ Other options can also be specified on the commandline, such as ``--host-pnor``
3335
which is documented in :ref:`flashing-firmware`.
3436

3537
There is also a *per user* configuration file, at ``~/.op-test-framework.conf``
36-
where you can store global options, for example: ::
38+
where you can store global options, for example:
39+
40+
.. code-block:: ini
3741
3842
[op-test]
3943
smc_presshipmicmd=foo
@@ -207,7 +211,9 @@ This can be useful for test development/debug as well as testing the qemu
207211
simulator itself.
208212

209213
It may be useful to keep a configuration file with your qemu configuration
210-
in it for running tests. An example of such a configuration file is below: ::
214+
in it for running tests. An example of such a configuration file is below:
215+
216+
.. code-block:: ini
211217
212218
[op-test]
213219
bmc_type=qemu

0 commit comments

Comments
 (0)