OrgWiki/go-org-orgwiki
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
go-org-orgwiki/org/testdata/inline.org
Niklas Fasching da99094e20 Fix explicit line break parsing 
It's possible for the input to end right after the explicit line break,
i.e. after the second \. This currently leads to an out of range index into
input (as the for loop starts with start+2 and [start:start+1] is the \\).
2019-01-12 20:08:17 +01:00

1.5 KiB
Raw Blame History

  • emphasis and a hard line break
    see?
    also hard line breaks not followed by a newline get ignored, 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/da99094e202fce609081d78ca8d38d5b010a0274/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

  • timestamps

    • <2019-01-06 Sun>
    • <2019-01-06 Sun>
    • <2019-01-06 Sun 18:00>
    • <2019-01-06 Sun 18:00 +1w>
    • <2019-01-06 Sun 18:00>
    • <2019-01-06 Sun 18:00 +1w>