Jakub Narebski wrote: > Second, http://www.methods.co.nz/asciidoc/userguide.html#_text_formatting > ("7. Text Formatting", "7.1. Quoted Text") says (emphasizis mine): > > Word phrases `enclosed in backtick characters` (grave accents) are also > rendered in a monospaced font but in this case the enclosed text is > __rendered literally__ and is not subject to further expansion (see > inline literal). > > So yes, it is safe, and no, `{backslash}#` would not work. This is correct, but the behaviour you quote was introduced in a minor release of asciidoc (!!!). From 71c020c5: Disable asciidoc 8.4.1+ semantics for `{plus}` and friends asciidoc 8.4.1 changed the semantics of inline backtick quoting so that they disable parsing of inline constructs, i.e., Input: `{plus}` Pre 8.4.1: + Post 8.4.1: {plus} Fix this by defining the asciidoc attribute 'no-inline-literal' (which, per the 8.4.1 changelog, is the toggle to return to the old behaviour) when under ASCIIDOC8. So in fact with current settings in Documentation/Makefile, the brace escapes *are* expanded even within backticks. -- Thomas Rast trast@{inf,student}.ethz.ch -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html