mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-07 06:02:26 -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
|
@ -9,11 +9,11 @@ This page sets out the configuration changes made, with (not necessary complete)
|
|||
|
||||
1. sudo (``/etc/sudoers.d/qubes``):
|
||||
|
||||
.. code:: bash
|
||||
.. code:: text
|
||||
|
||||
Defaults !requiretty
|
||||
%qubes ALL=(ALL) ROLE=unconfined_r TYPE=unconfined_t NOPASSWD: ALL
|
||||
|
||||
|
||||
(...)
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ This page sets out the configuration changes made, with (not necessary complete)
|
|||
|
||||
2. PolicyKit (``/etc/polkit-1/rules.d/00-qubes-allow-all.rules``):
|
||||
|
||||
.. code:: bash
|
||||
.. code:: text
|
||||
|
||||
//allow any action, detailed reasoning in sudoers.d/qubes
|
||||
polkit.addRule(function(action,subject) { if (subject.isInGroup("qubes")) return polkit.Result.YES; });
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue