Denis Bitouzé

Sorry, the ⟨code⟩ snippet is rendered as `<literal>⟨code⟩</literal>`, not as `⟨code⟩`.

> Please test the following patch. Quite weird: with an up to date TeX Live 2022, the `pgfkeys.code.tex` file contains only 1160 lines: ```bash $ wc -l /home/bitouze/texlive/2022/texmf-dist/tex/generic/pgf/utilities/pgfkeys.code.tex 1160 /home/bitouze/texlive/2022/texmf-dist/tex/generic/pgf/utilities/pgfkeys.code.tex...

> I think Henri's patch is based on the latest [`pgfkeys.code.tex`](https://github.com/pgf-tikz/pgf/blob/master/tex/generic/pgf/utilities/pgfkeys.code.tex), which contains some not-yet-released changes. @muzimuzhi That's what I wanted to stress out :smile: > Nevertheless the key is...

@timhoffm Could be nice for this to be explicit instead of implicit. Maybe some TXS menu could provide an entry "Print PDF" which would display a window briefly explaining what...

> Closes #11556. > > @dbitouze could you check whether the workflow works in production using some fresh project (I don't have any way to test it now). Yes, I'll...

> Closes #11556. IMHO, this doesn't close this issue which is about “Document how sphinx's change detection works” since, AFAICS, this remains unclear.

> Ah, actually the issue should be renamed to something like "make gitlab CI workflow incremental" (since it was your main concern eventually) > > Concerning the way changes are...

> Sorry for the late reply. You're welcome! > 1. I still want to keep the original Sphinx image (at least it won't add an extra dependency or it doesn't...

> As for documenting, it should be a separate task. As I said, people don't bother about how it works until it fails. The issue is titled "document" but I...

> This is something I would like to say "yes". I assume you want this for `autodoc` where you could then change manually whatever `autodoc` has written right? Actually, no,...