Timeline for Is that the optional arguments that matters the expansion?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23 at 7:59 | vote | accept | Explorer | ||
| Feb 22 at 17:09 | comment | added | Explorer | I am still not sure about isn't that is to say it's NOT recommended to use unexpandable command inside NewExpandableDocumentCommand, could my usage of NewExpandableDocumentCommand in mwe a reasonable workaround or an exception? | |
| Feb 22 at 16:55 | vote | accept | Explorer | ||
| Feb 22 at 17:11 | |||||
| Feb 22 at 16:54 | comment | added | Joseph Wright♦ | @Explorer You will be fine - there are no docs for the pgf parser: I've read over the code for debugging purposes | |
| Feb 22 at 16:30 | comment | added | Explorer | That is to said, although NewExpandableDocumentCommand may cause problem with optional arguments, but in my case with pgf's unusual parse, it's okay to make unexpandable \node inside NewExpandableDocumentCommand,right? BTW, is there any related link introduce more about the unusual pgf parser?Thanks for yr kindness! | |
| Feb 22 at 15:47 | comment | added | Joseph Wright♦ | @Explorer Most of the time people want full expansion of everything - your case is unusual as pgf expands up to things it 'knows' - in your case \node | |
| Feb 22 at 11:59 | vote | accept | Explorer | ||
| Feb 22 at 16:49 | |||||
| Feb 22 at 11:58 | comment | added | Explorer | maybe I didn't fully understand that you mentioned "you are using a non-expandable command (\node) inside your definitions, so you can never have a fully-expandable situation here", as I use \node inside \NewExpandandableDocumentCommand, so I said "I can't use \NewExpandandableDocumentCommand`"... | |
| Feb 22 at 8:47 | comment | added | Joseph Wright♦ | @Explorer I don't see why you can't use \NewExpandandableDocumentCommand - it does what you want | |
| Feb 22 at 8:18 | history | answered | Joseph Wright♦ | CC BY-SA 4.0 |