« first day (4447 days earlier)      last day (336 days later) » 

6:33 AM
user image
6
 
 
2 hours later…
8:16 AM
@gusbrs Providing .cfg support means that is 'hidden' in a document: if the user has to load something explicitly, they know they are responsible for it
 
 
1 hour later…
9:38 AM
@JosephWright I get it, it may well become a can of worms. I did follow the good advice btw github.com/gusbrs/zref-vario/issues/1#issuecomment-1369259796. Thanks again!
 
 
4 hours later…
1:10 PM
@JosephWright I'm principally done with (most) of the work on expkv and could release it. But just today I thought "Why not make the planned expansion control even more concise" and now I'm somewhat unsure whether I should release the current plans or rework stuff to get it shorter (well, it'd be just expansion control has to be started with a specific prefix or not, so either exp|o: foo = bar to expand the value once or only o: foo = bar).
 
2:03 PM
@Skillmon You probably need user feedback, so release and be prepared to change with a compatibility layer?
siunitx v3.2.0 on the way to CTAN with the new SI prefixes :)
2
 
 
2 hours later…
3:56 PM
@SeanAllred your "quiet period"?
user image
3
 
 
1 hour later…
5:14 PM
@JosephWright well, there are (to my knowledge) currently three packages that support things like this: pgfkeys (with /.expand once), options (also with /.expand once), and yax (full expansion with a prefix e:). So in the "prefix"-land the only other package also uses no long flag. The issue I have with it is, that I have to implement it backwards compatible. That's no issue in the case of setting defined keys (just check the key is defined, otherwise search for expansion), (1/2)
but in \ekvparse (equivalent to \keyval_parse:nnn) things are obviously more complicated and using the less-likely input is bound to less likely introduce backwards incompatibility. (2/2)
 
 
2 hours later…
7:14 PM
@JosephWright and "with a compatibility layer" is something I'd like to avoid. I took a quick look and all the packages which are currently using \ekvparse are mine and in those the rule I'm currently thinking of (the colon has to be followed by additional tokens) will work. There is also semantex which can be configured to use \ekvparse internally but doesn't by default, and that one doesn't use colons in key names as far as I saw.
 
7:28 PM
watch out Tikz, there is a new open source package which one can program in to generate graphics and animations using python. Much easier code to read and it is OOP also. manim
 
@Nasser It does look quite interesting depending on your needs. But for most people the direct integration into a document is a big plus for using TikZ.
 
8:11 PM
@Nasser Nice! I thought that was only for animations.
 
8:32 PM
@Nasser TikZ is long obsolete, I released pxpic on 2021-01-13.
4
 
@mickep I am not that familiar with manim as I found about it myself 2 days ago only, but there is a way to save images based on this. It also uses Latex for math which is good.
@Skillmon nice package.
 
9:35 PM
@Skillmon haha, beautiful
 
 
2 hours later…
11:40 PM
HI, I was surprised to find out that Frank Mittelbach does not have a Wikipedia page. Does anyone here have a good reference with some "CV milestones" that I can use to create a Wiki page for him?
(or I am not able to find the Wiki page, which is also an option)
 

« first day (4447 days earlier)      last day (336 days later) »