go-org-orgwiki/org/testdata/inline.org
Niklas Fasching d1054063cf Anchor inline regexps and improve sub/super-script
The regexps are meant to extract a match immediately following the cursor - the
anchor should have been there from the beginning...

Also empty sub/superscript doesn't make sense - nested sub/superscript does
make sense but yagni.
2018-12-20 15:43:16 +01:00

1.2 KiB

  • emphasis and a hard line break
    see?
  • .emphasis with dot border chars.
  • emphasis with a slash/inside
  • emphasis followed by raw text with slash /
  • ->/not an emphasis/<-
  • links with slashes do not become emphasis: https://somelinkshouldntrenderaccidentalemphasis.com/ emphasis
  • underlined bold verbatim code strikethrough
  • bold string with an *asterisk inside
  • multiline emphasis is supported - and respects MaxEmphasisNewLines (default: 1) so this is emphasized /but this is not emphasized/
  • empty emphasis markers like ++ // __ and so on are ignored
  • use _{} for subscriptsub and ^{} for superscriptsuper
  • links

    1. regular link https://example.com link without description
    2. regular link example.com link with description
    3. regular link to a file (image) /OrgWiki/go-org-orgwiki/media/commit/d1054063cf075da74de4107c989a9f0898169c9f/org/testdata/my-img.png
    4. regular link to a file (video)
    5. regular link to http (image) http://placekitten.com/200/200#.png
    6. regular link to https (image) https://placekitten.com/200/200#.png
    7. regular link enclosed in [] [https://www.example.com] [example.com]
    8. auto link, i.e. not inside \[[square brackets]\] https://www.example.com