Timeline for The current status of "cleveref"
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2024 at 15:46 | comment | added | AlMa1r | If users load cleveref after cleveref-forward, they are themselves to blame. In my opinion, nobody should use the unpatched official cleveref any longer, and failing on loading it is the right thing to do. Although the additional compilation may negligible for one person compiling once, these times sum up to tons of CO₂, and they also sum up noticeably if you compile many documents in a batch over and over again in the course of the years. | |
| Jun 19, 2024 at 21:00 | comment | added | AlMa1r | Concerning cleveref-foward, consider inserting the code of cleveref into your package rather than using cleveref. This would allow you to actually replace the wrong code at the places it should be replaced rather than calling the wrong code and patching it subsequently (which wastes some running time whenever a document uses cleveref-forward). | |
| Mar 14, 2024 at 11:37 | history | made wiki | Post Made Community Wiki by Jinwen | ||
| Mar 13, 2024 at 13:51 | history | answered | Jinwen | CC BY-SA 4.0 |