* Most of text blocks are in fact output blocks
* On qubes-iso-building.rst, try to get something correct for console
lines starting with a comment
* Fixing a wrong :menuselection: item.
Statistics:
685 console
79 text
44 bash
35 output
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
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 is plain rename without changing content, to help git track files
history.
Do not touch files that are going to be removed during conversion.
Thanks @parulin for the idea!
In a discussion on Qubes OS forum, it was decided that I should add some extra text about the netmask, and an example for Network Manager. The purpose being to make the procedure much clearer.
There are two images to go into the text, but I don't understand how to do that yet. I have used '>' at those points. Please advise.
Francis.
Although sys-gui (and its variants sys-gui-gpu and sys-gui-vnc) are clearly marked to be used by advanced users only, there are some limitations that may go beyond the expectations of an advanced user.
This updates the documentation to contain some known issues that probably don't have a quick fix.
