| 15 Jan 2022 |
|  hardyowo joined the room. | 21:45:38 |
| 16 Jan 2022 |
| hardyowo changed their profile picture. | 02:59:29 |
| 17 Jan 2022 |
 Github [@hmenke:matrix.org] | [pgf-tikz/pgf] hmenke closed issue #1122: Form-only patterns have no specified color [closed] - https://github.com/pgf-tikz/pgf/issues/1122 | 10:44:19 |
| 18 Jan 2022 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgf] fritzw opened issue #1128: Choice key handler with deferred execution of code [open] - https://github.com/pgf-tikz/pgf/issues/1128 | 16:19:01 |
| Github [@hmenke:matrix.org] | [pgf-tikz/pgf] fritzw edited issue #1128: Choice key handler with deferred execution of code [open] - https://github.com/pgf-tikz/pgf/issues/1128 | 16:22:37 |
| 22 Jan 2022 |
 hmenke | The definition of the /.expanded key handler currently is:
\pgfkeys{/handlers/.expanded/.code=\edef\pgfkeys@temp{#1}\expandafter\pgfkeys@exp@call\expandafter{\pgfkeys@temp}}
| 10:26:28 |
 Github | https://github.com/pgf-tikz/pgf/issues/1 : [v0.96] node example doesn't work | 10:26:28 |
| hmenke | I wonder whether that should be switchted to use \expanded. | 10:26:45 |
| hmenke | It would also be nice to have a handler for f-type expansion, but I don't know what to name it. | 10:27:08 |
| Github [@hmenke:matrix.org] left the room. | 10:28:05 |
| Github left the room. | 10:28:16 |
| hmenke | This GitHub bot is way more annoying that useful. I just wanted to have notifications of new issues and PRs but it's not possible to turn off all the other noise. | 10:29:07 |
 muzimuzhi | In reply to @hmenke:matrix.org
I wonder whether that should be switchted to use \expanded. \edef will half the number of #s, but \expanded won't, so it's actually a breaking change.
latex3 uses x for \edef, e for \expanded, and f for \romanumeral. To keep the compatibility, maybe just add three more handlers like /.x expanded, /.e expanded, and /.f expanded? It's a bit ugly, but causes less problems.
| 10:52:05 |
| hmenke | muzimuzhi: Fair point. So touching /.expanded is out of the question. | 10:58:23 |
| muzimuzhi | hmenke: Some of pgf's internal use of /.expanded can (still) switch to the \expanded based new handler. Here "some" means when we're sure that the value won't contain macro args ##n. | 11:03:30 |
| 23 Jan 2022 |
|  bigbroc joined the room. | 16:59:08 |
| 24 Jan 2022 |
| bigbroc | What is the rationale for definpgrinterruptpathing\graph as \def\graph{\path graph} when just slightly down into parsing of graphs we enclose everything in \pgfinterruptpath? | 21:38:22 |
| bigbroc | * What is the rationale for defining \graph as \def\graph{\path graph} when just slightly down into parsing of graphs we enclose everything in \pgfinterruptpath? | 21:38:44 |
| bigbroc | Maybe just to fulfill “every drawing operation in pgf is basically a \path?” | 21:53:03 |
| 25 Jan 2022 |
| muzimuzhi | In reply to @bigbroc:nerdsin.space
Maybe just to fulfill “every drawing operation in pgf is basically a \path?” I guess so. | 13:22:40 |
| 26 Jan 2022 |
| hmenke | bigbroc: Asking about design decisions is always difficult because Till is not here and none of us was involved in most of the original development. | 13:31:00 |
 samcarter | In reply to @hmenke:matrix.org
bigbroc: Asking about design decisions is always difficult because Till is not here and none of us was involved in most of the original development. My personal conspiracy theory is that COVID was invented just to safe Till from having to answer all my why-does-beamer-questions at the 2020 Dante meeting :) | 13:58:36 |
| 30 Jan 2022 |
| muzimuzhi | In reply to @hmenke:matrix.org
muzimuzhi: What do you think about requiring Conventional Commits for PGF? hmenke: Since Conventional Commits has been applied for a while with a tacit agreement, maybe it's time to mention and require it in PR template. This could save us from reminding new contributors. | 18:36:41 |
| hmenke | muzimuzhi: Yes, we could certainly formalize the requirements for commit messages a bit. | 19:15:40 |
| hmenke | muzimuzhi: What you pushed was exactly the same that I pushed. Only my changelog update got lost, but I quickly cherry-picked that on top of your branch. | 19:32:33 |
| muzimuzhi | In reply to @hmenke:matrix.org
muzimuzhi: What you pushed was exactly the same that I pushed. Only my changelog update got lost, but I quickly cherry-picked that on top of your branch. I was too sensitive to "Run failed" emails 😢 | 20:57:05 |
| muzimuzhi | In reply to @hmenke:matrix.org
muzimuzhi: Yes, we could certainly formalize the requirements for commit messages a bit. Perhaps also a note like
for simple manual typo corrections it's as easy as starting your commit message with doc: (or fix: ? i'm not sure)
since most new contributions are manual typo fixing
| 21:01:12 |
| muzimuzhi | In reply to @hmenke:matrix.org
muzimuzhi: Yes, we could certainly formalize the requirements for commit messages a bit. * Perhaps also a note like
for simple manual typo corrections it's as easy as starting your commit message with doc: (or fix: ? i'm not sure)
since <s>most</p> a large portion of new contributions are manual typo fixing
| 21:04:39 |
| muzimuzhi | * Perhaps also a note like
for simple manual typo corrections it's as easy as starting your commit message with doc: (or fix: ? i'm not sure)
since <s>most</s> a large portion of new contributions are manual typo fixing
| 21:04:46 |
 Romano Giannetti | Hi --- I am not sure what the protocol is here... so please don't kill me. First post here, hi everybody | 21:27:43 |
