« first day (3709 days earlier)      last day (170 days later) » 

cfr
12:48 AM
Nadolig llawen pawb!
(Code now compiles without error.)
 
@cfr -- But does this imply that the cat was responsible for the error?
 
 
4 hours later…
cfr
5:01 AM
@barbarabeeton No. The cat was never in this version, but the code assumed she was, so the node with forest@id@cath failed to refer. If the cat had been there, it would have been fine.
@barbarabeeton I suppose the cat could be blamed for her absence.
@barbarabeeton However, there is something odd about this tree. Did I really have it flare out at the bottom like that? Weird.
 
 
3 hours later…
8:10 AM
quack
@samcarter_prepared_for_xmas ooh <3
 
 
2 hours later…
10:18 AM
@DavidCarlisle 10 users yesterday !
@PauloCereda Quack
 
@JosephWright ooh a duck
 
yo'
10:54 AM
@PauloCereda ohh two ducks!
 
@yo' ooh
 
11:17 AM
@yo' QUACKK
 
yo'
@JosephWright you just woke me up from my winter sleep :D
 
11:47 AM
baa!
 
@Plergux hi sheep person!
 
@PauloCereda hi duck person! :D
 
@Plergux ooh
 
yo'
12:29 PM
Wow, rude of you to regift literally every gift that you or anyone else has ever received.
5
 
12:41 PM
I've got headphones too! :-)
 
macOS is no more
My iMac is now about to run Linux
 
 
1 hour later…
2:13 PM
@PauloCereda Ack
 
@JosephWright It was tricky to keep a very old system. :(
 
 
2 hours later…
3:50 PM
@StephanLehmke Hi! Long time no see! I hope you and your family are safe!
 
@PauloCereda Hi all! Merry Christmas!
 
@StephanLehmke Merry Christmas!
 
Yea, we're all well and safe so far, though quite cautious. Cases skyrocketing right now in Germany.
Zoom christmas party with my parents two days ago, though they only live 50km away ;-)
Learning Elixir at the moment.
 
@StephanLehmke oh no, another Brazilian-based language. :)
 
Thanks for asking. How about you?
 
3:54 PM
We are fine, and worried at the same time. Cases are also skyrocketing in Brazil, and numbers are way worse now than in the beginning...
 
@PauloCereda Well everything good seems to come out of Brazil :-)
 
@StephanLehmke ooh <3
@DavidCarlisle ^^
@StephanLehmke I was so happy that I was finally going to Germany in March to attend the Dante meeting... but then...
 
@PauloCereda Yea, shit happens :-( I was going to exhibit on DRUPA for the first time after 12 years...
@PauloCereda There will be a next opportunity.
@PauloCereda Do you know Elixir?
 
@StephanLehmke oh my
@StephanLehmke next year, fingers crossed. :)
@StephanLehmke Only a few reports... I am now learning Kotlin. :)
 
@PauloCereda Ah, Ok. I looked at it when deciding to migrate from Python+Django, but Elixir looked more promising for my purpose.
 
4:03 PM
@StephanLehmke Ah it's powered by the Erlang VM, I guess. :)
 
@PauloCereda Yea, that. Hopefully able to do high load parallel and distributed computing.
 
@StephanLehmke cool, and hot swap!
 
 
7 hours later…
10:54 PM
I have a very basic question of expl3, so I hope the answer is super simple to understand it :)

If I have two commands
\NewDocumentCommand \checkRow { s m m m }
and
\NewDocumentCommand \getRow { s m m m }

Can I put both of them inside a third command (e.g. \NewDocumentCommand \getCheckedRow { s m m m ) such that the

1- the four arguments of the third parent command will be populated to the two children commands
2- the execution of the third command means the first command will be executed and after its successful execution the second one will be executed.
 
11:07 PM
@Diaa well if the arguments the two commands should get are the same you can naturally combine them. You will have to test for the star.
 
11:26 PM
How to combine them?
Is it something like

\NewDocumentCommand \parentcommand { s m m m )
{ \firstcommand { #1 #2 #3 #4 }
{
<first command code>
}
\secondcommand { #1 #2 #3 #4 }
{
<second command code>
}
}
 
@Diaa why the code? your commands are already defined aren't they?
 
11:56 PM
Yes, they are
So, they should be like

\firstcommand { s m m m }
{
<first command code>
}

\secondcommand { s m m m }
{
<second command code>
}

\NewDocumentCommand \parentcommand { s m m m )
{
\firstcommand { #1 #2 #3 #4 }
\secondcommand { #1 #2 #3 #4 }
}
 

« first day (3709 days earlier)      last day (170 days later) »