mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-09 15:12:41 -04:00
Correct code-block lexers
Changing `bash` lexer to `console` because it is appropriate most of the time. Then after a manual review, some lexer have been changed. I used `text` each time I was unsure, and for prompt outputs. The page `/developer/building/qubes-iso-building.rst` still need to be reviewed (look for lines starting with `$ #`). I'm not sure about the Windows pages, should we use [doscon](https://pygments.org/docs/lexers/#pygments.lexers.shell.MSDOSSessionLexer) or `powershell`? Is there an appropriate lexer for `guid.conf` content? **Statistics - Before** 870 bash 9 python 9 c 2 yaml **Statistics - After** 684 console 111 text 44 bash 16 yaml 9 systemd 9 c 8 python 4 ini 4 doscon 2 markdown 2 desktop 1 xorg.conf 1 xml+jinja 1 xml 1 kconfig 1 html This suggests that the default lexer should be `console`.
This commit is contained in:
parent
b53776e1eb
commit
ba399ac488
98 changed files with 1022 additions and 1029 deletions
|
@ -15,7 +15,7 @@ For simplicity, these instructions will refer to copying/moving a single file, b
|
|||
|
||||
3. If the target qube is not already running, it will be started automatically, and the file will be copied there. It will show up in this directory (which will automatically be created if it does not already exist):
|
||||
|
||||
.. code:: bash
|
||||
.. code:: text
|
||||
|
||||
/home/user/QubesIncoming/<source_qube>/<filename>
|
||||
|
||||
|
@ -28,13 +28,13 @@ For simplicity, these instructions will refer to copying/moving a single file, b
|
|||
|
||||
The same operations are also available via these command-line tools:
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
qvm-copy [--without-progress] file [file]+
|
||||
|
||||
|
||||
|
||||
.. code:: bash
|
||||
.. code:: console
|
||||
|
||||
qvm-move [--without-progress] file [file]+
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue