[pve-devel] [PATCH pve-docs] Escape curly brackets inside single quotes (')

Emmanuel Kasper e.kasper at proxmox.com
Thu Sep 8 11:51:46 CEST 2016


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
---
 pveum.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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.
 
-- 
2.1.4




More information about the pve-devel mailing list