Oliver Kopp
Oliver Kopp
> Am I misunderstanding something ? Yes. Proposal: Write documentation for each CLI command to our user-documentation repository. Moreover, think of tests. As simple as expected --help output. Check for...
> Test logic, not strings. In this case, some "grep"ing would make sense. Checking if the help output does not contain the export formats. (We do this in fetcher tests...
> the `--output` option is more indicative of export behavior than `--output-format` while checking among the option names. Unfortunately, not. `--output` specifies the output file. In our case **BibTeX**, which...
> In that case, if we look at commands with `--input-format` and `--output-format` options, it works except for the `search` command, which can convert the query results if an output...
Similar issue for downloading nightly builds:  Should I open a new issue for this? (The releases are from 2023 and I think, these are outdated)
With `mylatexformat` (source: https://tex.stackexchange.com/a/687427/9075): luahbtex -ini -jobname=mwe "&lualatex" mylatexformat.ltx mwe.tex ``` (C:/MiKTeX/tex/generic/markdown/markdown.tex ! Use of \??? doesn't match its definition. \??? ! LaTeX Error: Access to an entry beyond an...
> Interesting. Do you have any idea if this is a natural limitation of the approach used by mylatex and mylatexformat or if this is something that we can fix...
> Hmm, you say that the general structure is too technical. You mean the blog post or documentation? I don't know, who "you" is here. - I meant the user...
> Oh, and also why AI is not `advanced`? I didn't find the text I wrote, therefore, I rephase. 1. I assume a user of the documentation DOES NOT follow...
> What about this: I miss the "why" there. AKA "reasoning" AKA providing rationales. My reasoning for one page was: > I agree that detail configurations are not meant for...