Benct Philip Jonsson

> > An option for next, previous, and up links (using arrows) would be nice. > I think this is a job for the template, assuming each file would be...

@jgm so the main difference between Para and Plain is that Plain avoids added whitespace in lists and tables? Is that true of TeX output formats as well? In particular,...

- I don't think the `[^1]` vs. `[^a]` version will work as the current syntax for footnotes is actually `[^arbitrary_identifier]` so different 'magic characters' instead of/in addition to `^` is...

The problem with `[^a]` vs. `[^1]` is that it breaks backwards compatibility in a bad way. The possibility to use arbitrary note identifiers is a valuable feature: while working on...

You could place a marker character as the first char of the footnote _text_, optionally followed by an all-alphanumeric id and then a space. Perhaps you could put it in...

Wow @charlesangus comment jogged my memory! In the years since 2014 I have written two filters in Perl which addressed this issue. The first used the idea of having a...

As of 2019-07-30 there is no such issue as far as I can see so I'll go ahead and create one.

> In general, there seems to be an issue with code highlighting of inline code blocks within links. Yes there is. IMHO the best solution is probably not to highlight...

One thing which could definitely be dropped is highlighting of indented blocks which gives way too many false positives. Now that Pandoc supports fenced code blocks there is no reason...

I just want to say two/three things: 1. I really hope you won't drop support for regular Vim. Neovim has dropped support for perl which I depend on in some...