χristoφe Демко
χristoφe Демко
I think I'm globally ok *but* it lacks some features: ~~~ ``` {#identifier .env arg=w1 arg=w2 on=w3 opt=w4 convert.arg="*italic*" convert.opt="**bold**"} ... ``` ~~~ should be translates to ~~~ \begin{env}{w1}{w2}{\emph{italic}}[w4][\textbf{bold}]\label{identifier} ......
The issue is that I use [panflute](http://scorreia.com/software/panflute) to parse the data and panflute considers attributes as a python dict (without duplicates). See . ~~~python >>> from panflute import convert_text >>>...
When studying https://texdoc.org/serve/xparse/0, it seems that we should have a clear way to use these LaTeX3 new feature
See #192
I'm not against the idea if it makes things easier for users. However, I'm thinking more along the lines of this syntax: ~~~yaml pandoc-latex-environment: noteblock: [class1, class2] ~~~ means that...
I have the same kind of issue using only `hatch-vcs`: ~~~toml [tool.hatch.envs.hatch-test] extra-dependencies = [ "myproject.docs @ file://extra.docs/" ] ~~~ in the `extra.docs` folder, I have a `hatch_build.py` file: ~~~python...
I have a tiny sample: ~~~shell $ unzip sample.zip $ cd sample $ hatch build dist/sample-0.0.0.tar.gz dist/sample-0.0.0-py2.py3-none-any.whl $ hatch run docs:build Sphinx v8.2.3 en cours d'exécution Environment `docs` is not...
Perhaps this could be specified in the documentation?