markdown: more tweaks #3124
markdown: more tweaks #3124
Conversation
| Apart from the RPCs enumerated above, some classes have additional RPCs | ||
| associated with them. For example, the `VM` class has RPCs for cloning, | ||
| suspending, starting etc. Such additional RPCs are described explicitly | ||
| in the API reference. |
ocaml/doc/wire-protocol.md
Outdated
| `int`, and in each case the keys of the maps are stringified as | ||
| above. For example, the `(string -> double) map` containing the mappings | ||
| _Mike → 2.3_ and _John → 1.2_ would be represented as: | ||
| _Mike -> 2.3_ and _John -> 1.2_ would be represented as: |
There was a problem hiding this comment.
Does the arrow here appear properly without being interpreted in weird markdown related ways?
There was a problem hiding this comment.
I think the html notation in normal (non code-block) text is safer - what is the reason for changing it?
There was a problem hiding this comment.
Ok, it seems the output differs per system... No problem. If I remember well there are some more instances of → in the markdown_backend.ml you may want to change.
There was a problem hiding this comment.
Oh, I see one more indeed...
Btw, I'm also trying out the unicode character (→).
There was a problem hiding this comment.
Given the difference per system we may be safer with -> after all; or even -> presuming the latter looks ok for you (may be worth double-checking the rest of the escaped characters in markdown_backen.ml).
| ['OpaqueRef:1', 'OpaqueRef:2', 'OpaqueRef:3', 'OpaqueRef:4' ] | ||
| >>> records['OpaqueRef:1']['name_label'] | ||
| 'Red Hat Enterprise Linux 7' | ||
| ``` |
kc284
left a comment
kc284
left a comment
There was a problem hiding this comment.
Ok, happy with it - could you also squash the commits (which I forgot to do when I merged the previous PR)
The `→` code does not become an arrow when I build the PDF. Signed-off-by: Rob Hoes <rob.hoes@citrix.com>
This ensures that chapter headings appear correctly. Signed-off-by: Rob Hoes <rob.hoes@citrix.com>
4 participants
No description provided.