edukisto

The [`--loader`/`--experimental-loader`](https://nodejs.org/api/cli.html#--experimental-loadermodule) flag ```bash NODE_OPTIONS="--experimental-loader ts-node/esm" npx webpack configtest ``` offers a solution ```text ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`: --import 'data:text/javascript,import { register }...

@bloudraak, I don’t think it’s a `pandoc-include-code` issue. Since `gfm` (GitHub Flavored Markdown) doesn’t allow attributes in curly braces, an extension is required. Try `gfm+attributes`. I can’t check it with...

@tobiasdiez, what do you think about the following solution? **a.md:** ``` A ``` **b.md:** ``` B ``` **plan.lst:** ``` a.md b.md ``` **Console input:** ```bash pandoc $(cat plan.lst) ``` **Console...

It seems to me that it is necessary to clarify that `#` and `;` are special characters that require escaping in section names, keys and values. An unescaped character makes...

Below are some examples. [EditorConfig for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig) v0.16.4 ignores section names with unescaped `#` or `;`. Properties of these sections get carried over to the previous section. If...

It is clear that developers implement non-standard inline comments at their own risk. But... 1. > “Section **header**... may contain **any** characters between the square brackets”. > “Inserting a `#`...

@florianb, @xuhdev, the main problem is that the specification implicitly classifies `#` and `;` as special characters. These characters are not recommended for usage, but this is what makes them...