diff options
| author | Kaz Kylheku <kaz@kylheku.com> | 2023-06-04 07:10:30 -0700 |
|---|---|---|
| committer | Kaz Kylheku <kaz@kylheku.com> | 2023-06-04 07:10:30 -0700 |
| commit | da474f980acefdb93040615fbb850448b4525b51 (patch) | |
| tree | 0afc533395967eff6c98b774b3722f59490e5a4a | |
| parent | acff34d5223eb884aa00a4a77b44c2ad8f262829 (diff) | |
| download | tl-who-da474f980acefdb93040615fbb850448b4525b51.tar.gz tl-who-da474f980acefdb93040615fbb850448b4525b51.tar.bz2 tl-who-da474f980acefdb93040615fbb850448b4525b51.zip | |
README: put some code in code blocks.
* README.md: Some code snippets containing HTML escapes
are not put in backticks and so those escapes are
being rendered.
| -rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -132,9 +132,10 @@ Here are the differences to be aware of: "<a href='https://example.com'>malicious here</a><a href='blah'>click me</a>" Not escaping constant material is error-prone. - The CL-WHO user has to remember to write (:div "black&white") - whereas the TL-WHO user just writes (:div "black&white"); the & - escape is produced by TL-WHO. + + The CL-WHO user has to remember to write `(:div "black&white")` + whereas the TL-WHO user just writes `(:div "black&white");` the + `&` escape is produced by TL-WHO. * TL-WHO provides a `noesc` syntax. When the value of an attribute is expressed as `(noesc <expr>)`, escaping is disabled: |