Timeline for Generating a list with macros using tasks package
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2016 at 0:50 | answer | added | egreg | timeline score: 1 | |
| Sep 1, 2015 at 7:39 | comment | added | cgnieder |
There are at least two other questions asking the same thing about tasks on this site...
|
|
| Jun 2, 2015 at 18:51 | history | edited | feculededentier |
Added "external-files" tag to the question
|
|
| Jun 2, 2015 at 18:41 | answer | added | feculededentier | timeline score: 0 | |
| Jun 1, 2015 at 13:07 | comment | added | feculededentier |
The macros seem unnecessarily complicated in the MWE, but I am working on a very customized "exercise-answer" type package for my colleagues, and the lists are built "on-the-fly" by one environment (exercices) and two macros (\question and \sousquestion). The definitions in the MWE above are as I need them in the actual code, but I don't believe they affect the MWE in any way.
|
|
| Jun 1, 2015 at 5:59 | comment | added | Werner♦ |
One problem with your macro-approach is that the tasks environment is defined under environ and therefore needs an explicit \end{tasks}; the tasks environment captures its contents before processing it.
|
|
| Jun 1, 2015 at 5:35 | comment | added | Werner♦ |
You don't mention anything about the requirement for \macroone, \macrotwo or \macrothree to keep/use its arguments. Are they really necessary? If so, could you please provide a use-case that incorporates those?
|
|
| Jun 1, 2015 at 2:17 | history | asked | feculededentier | CC BY-SA 3.0 |