From: Emmanuel Kasper Date: Thu, 8 Sep 2016 09:51:46 +0000 (+0200) Subject: Escape curly brackets inside single quotes (') X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=commitdiff_plain;h=3b26ef9ed44063a6e65172a28b3e1f791af9713f;hp=8e5f15bedc5e7ac0785e289949fe304e95b8b260 Escape curly brackets inside single quotes (') text in backquotes (`) is not subject to asciidoc expansion but text inside single quotes (') is this behaviour led that '{vmid}' was somehow interpreted by asciidoc, and the whole line was not not rendered pveum.adoc was the only file with that problem as curly brackets are inside backticks in the rest of the documentation --- diff --git a/pveum.adoc b/pveum.adoc index 2f3584a..00f260a 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -103,8 +103,8 @@ Objects and Paths ~~~~~~~~~~~~~~~~~ Access permissions are assigned to objects, such as a virtual machines -('/vms/{vmid}') or a storage ('/storage/{storeid}') or a pool of -resources ('/pool/{poolname}'). We use filesystem like paths to +('/vms/\{vmid\}') or a storage ('/storage/\{storeid\}') or a pool of +resources ('/pool/\{poolname\}'). We use filesystem like paths to address those objects. Those paths form a natural tree, and permissions can be inherited down that hierarchy. @@ -219,7 +219,7 @@ Pools ~~~~~ Pools can be used to group a set of virtual machines and data -stores. You can then simply set permissions on pools ('/pool/{poolid}'), +stores. You can then simply set permissions on pools ('/pool/\{poolid\}'), which are inherited to all pool members. This is a great way simplify access control.