cabo
cabo
> > 1. approximate preservation of the presence (and therefore timing) > of congestion marks on the L2 frames used to construct an IP > packet; > > 2. a....
> Using `` within `` isn't a hack. Well, allowing both mixed content (span-level) and t (block-level) sure is, avoiding the h word, interesting. Giving them different semantics makes my...
Is it possible to link to the actual figure?
One problem is that ``` is not standard markdown. So the processor might be interpreting this as a code span (`foo`), not a code block (which would be ~~~ foo...
The cache lifetime for RFC, BCP, STD references is currently set at 86400*7 seconds, i.e., one week. I didn't want to make it much longer because this goes to bib.ietf.org,...
You can get some verbosity by setting the KRAMDOWN_PERSISTENT environment variable to "v", i.e. ``` export KRAMDOWN_PERSISTENT=v ``` Martin's config.mk seems to set that to "true" by default„so you should...
... and maybe add a "quiet" setting as well.
Oh yes. This has hit me already as well. I need to find out why that workaround was necessary and whether I can defeat it. Might need a couple of...
```` ``` ```` is a code span delimiter in markdown. The codeblock delimiter (fenced codeblocks) is ` ~~~ `. (Please see the source of this comment to see why ````...
The convention right now is that a commit comment indicates a release. See https://github.com/cabo/kramdown-rfc/commits/master/, which also gives you the commit comments for what changed (here, just one commit, but it...