Skip to content

v2.0.2

@Orc Orc tagged this 16 Nov 23:07
   listing of all of the runtime settings to the output file.
2. Add a couple of functions that write the current runtime configuration
   (either a flags value (`mkd_flags_are`) or of an MMIOT (`mkd_mmiot_flags`))
   to a FILE.    `markdown -VV` prints out the flags for now, and the
   functions are there for other people to use as they desire.
3. Change the autolink prefix to closer fit to the reference dingus;
   if a `<url>` has a known protocol prefix, it does not need a
   leading `//` after the prefix.
4. Add test cases for <> links (regular and markdown 1 compat), split
   the superscript tests out from smarty.t
5. Modify superscript grabbing so that it grabs parenthetical
   and alphanumeric blocks
6. Rework (again!) the guts of `linkylinky` to support markdown
   1.0.2b8-style `<`..`>` links: these are like the original
   format I implemented before I rolled them out while chasing
   compatability in that a url starting with '<' contains _all
   characters_ until an unescaped '>' is encountered.
7. Version 2.0.2; fix a glitch in new-style `[]` processing that
   would collapse two sequential new-style `[link]`s into one
   no matter how much space was between them.  The reference dingus
   only coalesces adjacent new-style `[link]`s together if they
   are physically adjacent or have one space between them.
Assets 2
Loading