| 15 Dec 2021 |
 Norbert Preining | Yes, that would be great. Maybe throw in the one or other you didn't specifically include in the article, but might be worth for a sufficient large user base. That is difficult the evaluate, I know, but you surely kind find a good balance. | 08:04:16 |
| Norbert Preining | The point is that the full list of all possible is overwhelming, so some "pre-selection" would be great. | 08:04:47 |
 Joseph Wright | In reply to @northface:matrix.org
The point is that the full list of all possible is overwhelming, so some "pre-selection" would be great. Done: I've summarised the variables I include in the text | 08:22:56 |
| Joseph Wright | Let's hope hmenke likes it! | 08:33:53 |
| 16 Dec 2021 |
 Github [@hmenke:matrix.org] | [pgf-tikz/pgf] HyunggyuJang opened issue #1109: For dvisvgm backend, position tracking gets broken upon coloring within node [open] - https://github.com/pgf-tikz/pgf/issues/1109 | 00:28:55 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgf] HyunggyuJang edited issue #1109: For dvisvgm backend, position tracking gets broken upon coloring within node [open] - https://github.com/pgf-tikz/pgf/issues/1109 | 00:40:44 |
 hmenke | I'd like to remove the experiments/ folder from the PGF repo. Does anyone have an opinion on whether it should be archived somewhere? After all it's still accessible in the Git history. | 08:42:59 |
 samcarter | In reply to @hmenke:matrix.org
I'd like to remove the experiments/ folder from the PGF repo. Does anyone have an opinion on whether it should be archived somewhere? After all it's still accessible in the Git history. Oh, please do this folder! The beamerbaseboxes.sty file regularly drives me crazy whenever I put the pgf repo in my texmf tree to experiment with different versions! | 09:45:14 |
| samcarter | In reply to @hmenke:matrix.org
I'd like to remove the experiments/ folder from the PGF repo. Does anyone have an opinion on whether it should be archived somewhere? After all it's still accessible in the Git history. * Oh, please do remove this folder! The beamerbaseboxes.sty file regularly drives me crazy whenever I put the pgf repo in my texmf tree to experiment with different versions! | 09:45:27 |
| samcarter | * Oh, please do remove this folder! The beamerbaseboxes.sty file regularly drives me crazy whenever I put the pgf repo in my texmf tree to experiment with different versions! :P | 09:45:48 |
| Joseph Wright | In reply to @hmenke:matrix.org
I'd like to remove the experiments/ folder from the PGF repo. Does anyone have an opinion on whether it should be archived somewhere? After all it's still accessible in the Git history. I like 'tidy' repos - that's after all what the history is for | 09:46:00 |
| Joseph Wright | In reply to @hmenke:matrix.org
I'd like to remove the experiments/ folder from the PGF repo. Does anyone have an opinion on whether it should be archived somewhere? After all it's still accessible in the Git history. I suspect it dates from a pre-Git workflow: with Git, the 'usual' way is to make a personal fork with a branch, after all | 09:46:35 |
| hmenke | Farewell, experiments/ | 09:49:57 |
| Custom widget added by hmenke | 11:31:27 |
| Custom widget removed by hmenke | 11:31:52 |
| 17 Dec 2021 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche opened issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:33:05 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche edited issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:33:37 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche edited issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:33:48 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche edited issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:34:35 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche edited issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:35:24 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgfplots] ptoche edited issue #414: "restrict y to domain=" is less versatile than "domain=" [open] - https://github.com/pgf-tikz/pgfplots/issues/414 | 13:36:46 |
| 18 Dec 2021 |
 muzimuzhi | hmenke josephwright Since a GitHub Actions workflow can contain multiple jobs and by default jobs in a workflow run in parallel, it seems several workflows is not a must? | 14:19:24 |
| hmenke | muzimuzhi: True but triggers are only per workflow and in the future we might want to limit when doc.yml runs. | 14:20:26 |
| hmenke | main.yml is already limited to tagged releases only. | 14:20:38 |
| muzimuzhi | ah different triggers, that's reasonable | 14:21:14 |
| muzimuzhi | Also I don't understand how main.yml gets the latest pgfmanual.pdf. All I can see is it uses actions/upload-artifact@v2. In my understanding it should first set workflow_run then use actions/download-artifact@v2 to download the latest manual. | 14:34:37 |
| hmenke | muzimuzhi: l3build ctan also builds the manual. | 14:36:44 |
| muzimuzhi | typing texdoc l3build and reading it... 🥲 | 14:39:34 |
| hmenke | I'm wondering whether we should resurrect the `doc/generic/pgf/extract.lua` script that I wrote some time ago to extract all `codexample`s from the manual to quickly get a large set of very broad tests of the codebase. | 16:35:25 |
| hmenke | The downside is that these are also fairly unspecific and potentially expensive. | 16:35:56 |
