Damien Ready

In case there is still doubt about the topic, I am highly in favor of document metadata being within the document. Is there some reason that the comment character could...

>One beautiful thing about this is that (with the addition of a single comma) it's a valid Lua table I love having a way to serialize data without a new...

If leaning on an existing format, the chief benefit is being able to read/write document metadata without a bespoke parser. Is StrictYAML codified where this would be an option in...

1) I do not like the idea of executable code in the document. Use cases of that nature seem more appropriate to an extension mechanism. If someone wants to embed...

Trying to think more holistically, an eventual goal of this markup is that non-programmers could adopt it in various places: blogs, academic papers, forums, etc. In which case, using an...

I use a monorepo, so that would immediately cause some awkwardness, all projects would inherit the same configuration. Similarly, I think it is nice if there is a default mechanism...

Default `.rtx.toml` and a standardized local override would be sufficient for my purposes, but I like the optional generic mechanism to pull in a different one if required. However, I...

Looking more closely at the dotenv-flow priority list, I see what you mean. I do not care for that implicit `.local` override if it matches the `RTX_ENV`, but I can...

Similarly, I would like to be able to include segments of non-djot documents. My specific use case would be referencing source code. If I want to reference a function in...

Keeping line numbers in sync is definitely a tricky point. My ideal interface would allow for the two workflows: - starting line number + [offset line count | final line...