Includes are relative to the path where the command-line is run, not of the source

[paulehoffman]

The file named in an {{:include is searched for relative to where the kramdown-rfc command is run, not relative to the file that it is being run on. Instead, they should be relative to the file that has the {{:include statement. (Yes, this would be a breaking change, but it would be the only way to make sense.)

[cabo]

To avoid a breaking change, we could do an include-relative.

[cabo]

For an include-relative, there also needs to be a way to handle kramdown-rfc being used in a pipeline (i.e., without any knowledge of where the actual input file(s) live(s)), which is for instance how i-d-template calls it.

[cabo]

Do you have an example repo that we could use as a benchmark?