TeX - TopAnswers

TopAnswers TeX

Meta

samcarter samcarter

7 tables

samcarter

7 fonts

samcarter

5 beamer

samcarter

5 **Ti*k*Z**

user 3.14159

5 graphicx

Skillmon

5 koma

Skillmon

5 fancyhdr

Skillmon

5 math

Skillmon

5 biblatex

Skillmon

5 classes

Skillmon

5 pandoc

Skillmon

5 context

Skillmon

5 latexmk

Skillmon

5 arara

Skillmon

5 luatex

Skillmon

5 xetex

Skillmon

5 pdftex

Skillmon

5 latex3

Skillmon

5 texlive

Skillmon

5 ctan

Skillmon

print statement debugging

programming

nsajko nsajko

9 It's almost always a bad idea not to provide a Minimal Working Example, so... you'll get what you deserve. :)

frougon

8 TeX has built in debugging means with the different `\tracing...` settings. You can specify with these to which level of detail you get information on what TeX is doing (different engines have extended these `\tracing...` macros beyond what Knuth originally built into TeX, but this answer is non-exhaustive in every way, instead I'll focus on what is interesting to see what a macro gets for arguments, and to what it expands).

Skillmon

7 The `unravel` package turns your TeX into a debugger in which you can step through macro expansions and assignments. It doesn't support all primitives though, for instance it can't be used to step through or over a `tabular` since the underlying `\halign` isn't supported, and using it across cell boundaries would most likely not work as well.

Skillmon

How and when to use expl3 *local* (as opposed to *global*) variables and assignment?

latex3 programming expl3

nsajko nsajko

12 As the documentation says, variables should be either _assigned_ locally or globally. However, `expl3` _declares_ all variables globally. I suspect the confusion arises as you are seeing `\<thing>_new:N` as an assignment, which while true at the underlying engine level is not what we mean in the documentation when we talk about the _programmer_ making an assignment.

Joseph Wright

8 I'd say the answer here is basically such: local variables respect scopes, while global variables don't. But:

nsajko

SoC Day 1: Special Pythagorean triplet 30

samcarter samcarter

12 \* This line is not a spoiler. \*

frougon

10 ASCII-duck wants to solve:

Skillmon

3 *no spoiler to be seen*

samcarter

SoC Day 4: Largest palindrome product 11

samcarter samcarter

7 \* This line is not a spoiler. \*

frougon

6 *no spoiler here*

samcarter

SoC Day 10: Integer right triangles 10

samcarter samcarter

6 *No spoiler*

samcarter

6 without sorting the values and using `lualatex`

CrazyHorse

SoC Day 9: Triangular, pentagonal, and hexagonal

samcarter samcarter

7 \* This line is not a spoiler. \*

frougon

7 \* This line is not a spoiler. \*

frougon

SoC Day 6: Circular primes

samcarter samcarter

7 Duck wants to solve again:

Skillmon

7 I compiled the following code using `pdflatex` after rebuilding the format with increased memory parameters (see below). Compiling the .tex file requires about 2 minutes on my old computer.

frougon

SoC Day 3: Number letter counts 18

samcarter samcarter

7 The following code uses:

frougon

6 *No spoiler*

samcarter

How to export and use a non-TeX rule with an arara-project? 6

निरंजन निरंजन

7 Instead of reinventing the wheel, simply use the build in `clean` rule from arara:

samcarter

Another factor could be that the meeting in Bonn also came with a big discount for Dante members and had the Dante general assembly on the day before. This might have encouraged additional attendees which are missing in Prague.

At Dante a couple of people mentioned that they are deterred by the relatively high conference fee. Maybe people saved up during the years of online conferences and then splashed out to go to Bonn, but can't afford to do this every year?

**If you'd like to come to TUG'24 in Prague and did not yet register, please do this as soon as possible. Also submitt talks if possible. At the Dante meeting it was mentioned that TUG'24 is at the risk of being cancelled due to too few registrations and talks submitted :(**

Follow-up to an [earlier message of mine](https://topanswers.xyz/transcript?room=347&id=174868&year=2024#c174868): [xz Outbreak (CVE-2024-3094) - Part 2](https://infosec.exchange/@fr0gger/112211836264840207) by Thomas Roccia. Nothing really new, “just” a synthetic single-page presentation of backdoor setup mechanisms we've known since the last weekend. Unrelated: if you had one of the infamous `liblzma` versions 5.6.0 or 5.6.1 on your system, some people [suggest](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068348) to rebuild the initramfs. This is unlikely to harm, at least...

that overview of the GitHub activity of the malicious user are very interesting and hint at the longterm planning of all of this (as well as the strange conversations you shared earlier). Very interesting read, again thanks for sharing!

[Explaining the xz backdoor to non-technical people](https://infosec.exchange/@masek/112189323619514361) (in German but there is a Translate button; [Nürburgring](https://en.wikipedia.org/wiki/N%C3%BCrburgring) is a complex with two automobile circuits, AIUI). :-)