Timeline for etoolbox conditionals with kvoptions string options
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 31 at 15:42 | comment | added | David Carlisle | do not use kvoptions for a new class. see texdoc clsguide for the built in latex option handler. similarly you do not need etoolbox, latex has better conditionals built in. | |
| Aug 31 at 13:33 | answer | added | Skillmon | timeline score: 2 | |
| Aug 31 at 11:57 | answer | added | Skillmon | timeline score: 3 | |
| Aug 31 at 11:37 | comment | added | Skillmon | It would be easier to help you if you provided a bit more context (a small MWE, showing what you try to do, even if it doesn't fully work). | |
| Aug 31 at 11:36 | comment | added | Skillmon | Don't use kvoptions in this day and age. | |
| Aug 31 at 10:03 | comment | added | Marijn | Could you provide a bit of starting code to work with, a simple class with one or two options, and a command that you want to define conditionally? | |
| Aug 31 at 10:03 | comment | added | Explorer | Have you given a glance on texdoc kvoptions's manual, in "sec.3 Example"? You may find example such as \DeclareBoolOption{print} and \ifMCS@print, which seemed highly related to your question statement. | |
| Aug 31 at 9:59 | history | edited | Explorer | CC BY-SA 4.0 | syntax md |
| Aug 31 at 9:29 | history | asked | jemhop | CC BY-SA 4.0 |