@Skillmon Well, it's more practical tutoring with @PauloCereda. I'm doing Rust coding and code review for a living, so giving feedback and pointers on some Rust code/issues is something I can help with ;)
@Skillmon Probably. But we don't have much insight into GitHub actions. And on GitLab, caching works (to the point that was discussed in my TUG talk). A certain kind of caching is simply not supported with the latest images as I outlined at TUG (and we definitely do not suggest pulling the latest image every time if you can avoid it).
@DavidCarlisle One can always try if stat -c '%W %n' * | sort gives a sorted list matching one's intuition on the system (file birth time is mostly closer than modification, depends if the file system supports it). One can loop through that as well.
@AlanMunn There is no portable way for creation because some file systems and unices do not feature this. On some systems ls will have a proper switch so show it and then you can post-process the ls output. But not a portable sh/bash way.
@DavidCarlisle And don't forget the jurisdictions where the date does not matter only the lifetime of the creator (which are technically not copyright jurisdictions but working on a different principle).
The mpxerr file indicates that the first line is ` %&latex` (i.e., starting with a space, preventing the %& parsing). However, I do not really get why the use of outputtemplate should have any influence on the space being inserted or not.
Anyone with MikTeX around? A user complained about the wrong arara version being distributed. Could anyone confirm that MikTeX distributes the wrong version?
@Skillmon I know that without [opt] you would usually omit braces. As I said, it's just personal habit to try to scope things when I have some modifying prefixes which I consider [opt] to be. As it already adds symbols, I don't feel the braces to be a visual burden or anything like that. But I guess you got your answer that probably “both allowed” is the approach to satisfy different habits in that regard ;)